-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Revert "[ci] Remove redundant variables in global CI config" #19721
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
base: master
Are you sure you want to change the base?
Conversation
This reverts commit 2f2a29b. It breaks the option hashing in our CI script.
While I agree that having removed these options changes the hash, does it also lead to clashes? Sorry @dpiparo, but I have to say it again 😄:
|
I'm not worried about clashes between platforms, but the problem is that changing a default in |
This makes total sense, but you also named a possible solution: 🙂 (Or we don't do incremental builds. 😉) |
Test Results 21 files 21 suites 3d 13h 32m 57s ⏱️ For more details on these failures, see this check. Results for commit 5832be3. |
This problem is that when someone changes Stephans proposed solutions both make sense to me! The drawback of hashing |
Coincidentally, the failues in 2025-08-22T06:22:41.0697191Z Possible C++ standard library mismatch, compiled with __GLIBCXX__ '20250804'
2025-08-22T06:22:41.0697518Z Extraction of runtime standard library version was: '20250812' |
cmake has an option to print all current options, so no need to concatenate maybe? That way it will not be sensitive to eg just adding a newline to that file |
We need the hash before actually running |
Couldn't you do:
Or is that adding too much time delay due to the extra temporary configure step? |
This reverts commit 2f2a29b. It breaks the option hashing in our CI script.