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

[CN] Make CN run both Z3 and CVC5 in CI, tidy up runner CI script #365

Merged
merged 4 commits into from
Jul 17, 2024

Conversation

septract
Copy link
Collaborator

@septract septract commented Jul 5, 2024

NOTE: depends on this PR in the cn-tutorial repo, which fixes a bug in the runner script handling of cn arguments.

This PR also significantly tides up the runner script and shifts most of the logic over to the cn-tutorial MakeFile, and fixes a bug that was stopping some tests from running.

@septract septract changed the title Make cerberus run both Z3 and CVC5 when testing examples in CI [CN] Make cerberus run both Z3 and CVC5 when testing examples in CI Jul 5, 2024
@septract
Copy link
Collaborator Author

septract commented Jul 5, 2024

TODO: perhaps do the same for the cerberus-local test suite (run by the tests/run-cn.sh script) ?

@septract septract changed the title [CN] Make cerberus run both Z3 and CVC5 when testing examples in CI [CN] Make CN run both Z3 and CVC5 in CI, tidy up runner CI script Jul 10, 2024
@septract
Copy link
Collaborator Author

CI now fails because z3 and cvc5 have different timing characteristics, so one example times out with cvc5. Annoying problem, unsure what to do about it.

@bcpierce00
Copy link
Collaborator

bcpierce00 commented Jul 10, 2024 via email

@dc-mak dc-mak requested a review from cp526 July 14, 2024 08:13
cp526 added a commit to rems-project/cn-tutorial that referenced this pull request Jul 17, 2024
@cp526 cp526 merged commit 58c5d3a into rems-project:master Jul 17, 2024
1 check failed
@cp526
Copy link
Collaborator

cp526 commented Jul 17, 2024

I've bumped up the timeout for now and merged this.

We would like the CI to find regressions in timing behaviour, though. So we'll probably want to extend our scripts to collect timing statistics and "publish" the results in a way that allows for easy comparison across commits + fail if the overall sum exceed some sensible limit.

@septract
Copy link
Collaborator Author

@cp526 Agreed, I made an issue to capture this idea here: rems-project/cn-tutorial#54

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.

3 participants