-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #629 #641
Conversation
.VERSION
Outdated
@@ -1,6 +1,6 @@ | |||
$Format:%d%n%n$ | |||
# Fall back version, probably last release: | |||
2.3.1 | |||
2.5.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a duplicate change with your other PR. If you were to have based this branch from master I can do an octopus merge later and merge both at once.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops. I just merged the other one and deleted the branch. I assume there's no problem with merging this one too. I would expect git
is smart enough to recognize the duplicate commit and only add in what's new. I hope it's ok if I go for it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Good catch.
Codecov Report
@@ Coverage Diff @@
## master #641 +/- ##
=======================================
Coverage 55.77% 55.77%
=======================================
Files 4 4
Lines 3159 3159
=======================================
Hits 1762 1762
Misses 1397 1397 |
I clicked "Update branch" and will merge this once the tests pass again. |
Summary of changes
Deleted '!' in environment variable evaluations in
report_results.sh
installation script.Rationale for changes
The previous fix didn't work for me on Lubuntu.
Additional info and certifications
This pull request (PR) is a:
I certify that
- Increasing test coverage for all feature-addition PRs
- Increasing test coverage for all bug-fix PRs for which there
does not already exist a related test that failed before the PR
- At least maintaining test coverage for all other PRs
- Ensuring that all tests pass when run locally
- Naming PR to indicate work in progress (WIP) and to attach the PR
to the appropriate bug report or feature request issue
- White space (no trailing white space or white space errors may
be introduced)
- Commenting code where it is non-obvious and non-trivial
- Logically atomic, self consistent and coherent commits
- Commit message content
- Waiting 24 hours before self-approving the PR to give another
OpenCoarrays developer a chance to review my proposed code