-
Notifications
You must be signed in to change notification settings - Fork 9
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
#2024: Fix CI issue with empty CXX standard variable #2032
Conversation
a208d31
to
c407c1e
Compare
The script changes are fine. Why do we need to add the FORCE option? |
Also, what's the relationship between this change and the error shown in the linked issue? |
I believe Cezary understands, given his quick approval, but it's helpful to write things down so the rest of us can follow later |
@PhilMiller Force option is for overriding the already existing value in |
It seems that if the variable is set with nonsense, we shouldn't carry on and try to do something that looks sensible. If it's a likely user mistake, we should detect it and report the error. Otherwise, I don't think we should try to compensate for a script bug that we know about and are fixing. Is there some subtlety here I'm missing? |
No, you are right. Ok so I'll remove the FORCE option. Scripts will not create that issue again and if user set some gibberish then it would fail as on the pipeline right now. |
Codecov Report
@@ Coverage Diff @@
## develop #2032 +/- ##
========================================
Coverage 84.47% 84.47%
========================================
Files 731 731
Lines 25847 25847
========================================
Hits 21834 21834
Misses 4013 4013 |
Setting the defaults fixes the script issues just fine. Cf #2025 for the build_cpp.sh |
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.
I'll close #2025 since this PR includes that and an additional fix.
Closes #2024