-
Notifications
You must be signed in to change notification settings - Fork 921
Increase test coverage for PQC and CMake #9637
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
Conversation
28edd71 to
1eeae37
Compare
eed1a9e to
d794ad8
Compare
|
retest this please |
d794ad8 to
bccc6db
Compare
|
I think the remaining failing CI tests are unrelated to this PR. |
|
Jenkins retest this please |
bccc6db to
b4e8473
Compare
|
Jenkins retest this please |
douzzer
left a comment
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.
Minor questions+quibbles.
Looks good otherwise.
b4e8473 to
08a5694
Compare
I addressed the CMake gate thing in the updated commit. The options in the PQ build are beneficial in my view, see comments. |
|
Retest this please |
* More PQC configurations * More CMake setups * Fix various bugs uncovered by these tests Added some missing feature additions to CMake to make the example `user_settings_all.` config file work for the CI test.
08a5694 to
14ce795
Compare
|
Jenkins restest this please |
Increase test coverage, mainly for stuff related to #9605 and #9608
These are mainly
SMALLconfigurations or some edge cases, which have been missing up to now but already caused some build failures (e.g. #9608).Added the functionality added in #9605 to the existing CMake CI tests. Also added a new test to verify the
user_settings.hfunctionality with CMake. For that, some missing features have been added to CMake to make the exampleexample/configs/user_settings_all.hconfig file work for the CI test.