Skip to content

test: use kani built-in --harness-timeout option #5252

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

roypat
Copy link
Contributor

@roypat roypat commented Jun 6, 2025

Set a per-harness timeout of 30 minutes. This should hopefully make it easier to debug scenarios where proofs end up hanging indefinitely, as we now no longer hit the pytest timeout, but instead a timeout built into kani (which should tell us what exact harness timed out).

Changes

...

Reason

...

License Acceptance

By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.

PR Checklist

  • I have read and understand CONTRIBUTING.md.
  • I have run tools/devtool checkstyle to verify that the PR passes the
    automated style checks.
  • I have described what is done in these changes, why they are needed, and
    how they are solving the problem in a clear and encompassing way.
  • I have updated any relevant documentation (both in code and in the docs)
    in the PR.
  • I have mentioned all user-facing changes in CHANGELOG.md.
  • If a specific issue led to this PR, this PR closes the issue.
  • When making API changes, I have followed the
    Runbook for Firecracker API changes.
  • I have tested all new and changed functionalities in unit tests and/or
    integration tests.
  • I have linked an issue to every new TODO.

  • This functionality cannot be added in rust-vmm.

roypat added 2 commits June 6, 2025 10:16
Set a per-harness timeout of 30 minutes. This should hopefully make it
easier to debug scenarios where proofs end up hanging indefinitely, as
we now no longer hit the pytest timeout, but instead a timeout built
into kani (which should tell us what exact harness timed out).

Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
Just so that we run the test when we change only the test itself.

Signed-off-by: Patrick Roy <roypat@amazon.co.uk>
Copy link

codecov bot commented Jun 6, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.90%. Comparing base (a93e9f2) to head (eb4991d).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5252      +/-   ##
==========================================
+ Coverage   82.84%   82.90%   +0.05%     
==========================================
  Files         250      250              
  Lines       26967    26967              
==========================================
+ Hits        22342    22356      +14     
+ Misses       4625     4611      -14     
Flag Coverage Δ
5.10-c5n.metal 83.33% <ø> (ø)
5.10-m5n.metal 83.33% <ø> (ø)
5.10-m6a.metal 82.55% <ø> (+<0.01%) ⬆️
5.10-m6g.metal 79.16% <ø> (ø)
5.10-m6i.metal 83.32% <ø> (ø)
5.10-m7a.metal-48xl 82.53% <ø> (?)
5.10-m7g.metal 79.16% <ø> (ø)
5.10-m7i.metal-24xl 83.28% <ø> (?)
5.10-m7i.metal-48xl 83.28% <ø> (?)
5.10-m8g.metal-24xl 79.16% <ø> (?)
5.10-m8g.metal-48xl 79.16% <ø> (?)
6.1-c5n.metal 83.38% <ø> (ø)
6.1-m5n.metal 83.37% <ø> (-0.01%) ⬇️
6.1-m6a.metal 82.59% <ø> (ø)
6.1-m6g.metal 79.16% <ø> (ø)
6.1-m6i.metal 83.37% <ø> (ø)
6.1-m7a.metal-48xl 82.58% <ø> (?)
6.1-m7g.metal 79.16% <ø> (ø)
6.1-m7i.metal-24xl 83.39% <ø> (?)
6.1-m7i.metal-48xl 83.39% <ø> (?)
6.1-m8g.metal-24xl 79.16% <ø> (?)
6.1-m8g.metal-48xl 79.16% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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.

1 participant