Skip to content

Conversation

@happz
Copy link
Contributor

@happz happz commented Dec 10, 2025

Tests that triggered reboots and restarts were given their full duration on every invocation. This behavior is most likely incorrect, a duration should apply to the whole test, no matter how many times it reboots a guest.

Patch adds Duration object which poses a strict deadline, derived from the test duration key. Unlike a timeout, it is not reset after guest reboot or test restart.

Pull Request Checklist

  • implement the feature
  • write the documentation
  • include a release note

@happz happz added bug Something isn't working step | execute Stuff related to the execute step labels Dec 10, 2025
@happz happz added this to planning Dec 10, 2025
@github-project-automation github-project-automation bot moved this to backlog in planning Dec 10, 2025
@happz happz moved this from backlog to review in planning Dec 10, 2025
@happz happz added the ci | full test Pull request is ready for the full test execution label Dec 10, 2025
happz added 4 commits January 1, 2026 19:59
Tests that triggered reboots and restarts were given their full duration
on every invocation. This behavior is most likely incorrect, a duration
should apply to the whole test, no matter how many times it reboots a
guest.

Patch adds `Duration` object which poses a strict deadline, derived from
the test `duration` key. Unlike a timeout, it is not reset after guest
reboot or test restart.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working ci | full test Pull request is ready for the full test execution step | execute Stuff related to the execute step

Projects

Status: review

Development

Successfully merging this pull request may close these issues.

4 participants