Skip to content
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

Merged
merged 2 commits into from
Dec 6, 2022

Conversation

thearusable
Copy link
Contributor

Closes #2024

@thearusable thearusable self-assigned this Dec 2, 2022
@thearusable thearusable force-pushed the 2024-fix-broken-pipeline branch from a208d31 to c407c1e Compare December 2, 2022 11:32
@thearusable thearusable marked this pull request as ready for review December 2, 2022 11:49
@PhilMiller
Copy link
Member

The script changes are fine. Why do we need to add the FORCE option?

@PhilMiller
Copy link
Member

Also, what's the relationship between this change and the error shown in the linked issue?

@PhilMiller
Copy link
Member

I believe Cezary understands, given his quick approval, but it's helpful to write things down so the rest of us can follow later

@thearusable
Copy link
Contributor Author

@PhilMiller Force option is for overriding the already existing value in CMAKE_CXX_STANDARD, without that CMake's set function will not modify the value. In our case it was incorrectly set to an empty string.
So now even if we set that variable to "" in the script then it will still work properly because it would override it with the default value of 14.
Previously there was also a small issue in the scripts which will pass "" when no value is set. Now they will set a proper default value.

@PhilMiller
Copy link
Member

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?

@thearusable
Copy link
Contributor Author

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
Copy link

codecov bot commented Dec 2, 2022

Codecov Report

Merging #2032 (286b290) into develop (5dff872) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop    #2032   +/-   ##
========================================
  Coverage    84.47%   84.47%           
========================================
  Files          731      731           
  Lines        25847    25847           
========================================
  Hits         21834    21834           
  Misses        4013     4013           

@stmcgovern
Copy link
Contributor

Setting the defaults fixes the script issues just fine. Cf #2025 for the build_cpp.sh

Copy link
Contributor

@stmcgovern stmcgovern left a 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.

@lifflander lifflander merged commit da71bac into develop Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Documentation pipeline is broken
5 participants