-
Notifications
You must be signed in to change notification settings - Fork 135
Fix nightly jobs running CBMC latest on the perf suite
#2954
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
jaisnan
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.
Tyvm!
tautschnig
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.
I’m sorry, but we’ll need to dig deeper to see how the build system should relate to that error.
Fair enough, I've started bisecting on the Dec 15 commits. |
|
The problem comes from PR diffblue/cbmc#5815, where Now, I'm not sure where to go from here. The first question that comes to mind is: why is this error not reproducible with |
|
When comparing the outputs of both build systems, I've realized that To confirm this, I made this change to the workflow, and then triggered the CI run. Both the Therefore, it's likely that these jobs aren't testing with the CBMC we're building, but the one that we install through the Still, this doesn't explain why the |
The Regardless, I've been able to determine that the CBMC being executed in the Unfortunately, I haven't been able to make the |
|
Apologies for having been very quiet on this. Failing with current CBMC HEAD should be expected at this time as the new major release being prepared for CBMC includes several breaking changes. We should either ignore the job’s failure, or disable it, or prepare a Kani branch and use that branch for our testing. |
Agree, #2952 just seems to be the first breaking change to be noticed. However, I think we need to at least change the |
The "CBMC latest" workflow is composed of two jobs (`regression` and `perf`) which perform testing with the most recent development version of CBMC. At present, the `regression` jobs are not actually testing with the CBMC that we build from source, but the CBMC installed through the setup scripts, as revealed in #2954. This PR changes the `regression` jobs so that they use `cmake` to build. This allows the runner to pick up the recently-built CBMC development version instead of the one installed through setup scripts, as it's done in the `perf` jobs. Unfortunately, [this CI run](https://github.com/adpaco-aws/rmc/actions/runs/7390380572) doesn't demonstrate the fix as it should due to an unrelated breaking change in the latest CBMC version. However, #2952 provides more context in case you need it.
As explained in #2952 , the nightly
perfruns started failing over the weekend with this error:Changing the build process for CBMC to use
makeinstead ofcmakeis enough for the error to go away. This action run shows how a successfulperfjob with the change in this PR.Resolves #2952
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.