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

Avocado-instrumented default timeout removal #5728

Merged
merged 1 commit into from
Oct 5, 2023

Conversation

richtja
Copy link
Contributor

@richtja richtja commented Jul 14, 2023

This will remove unsystematic timeout inside avocado-instrumented runner. This timeout has been set to 24 hours and users haven't had a way how to change it. Because we solved problems with task.timeout.running in #5383 and job-timeout in #5295 this default timeout is not needed anymore. After this change, the users will have more power over timeouts and will be able to run instrumented tests longer than 24 hours.

Reference: #5394

@richtja richtja added the bug label Jul 14, 2023
@richtja richtja requested a review from clebergnu July 14, 2023 09:42
@richtja richtja self-assigned this Jul 14, 2023
@richtja richtja linked an issue Jul 14, 2023 that may be closed by this pull request
@richtja richtja marked this pull request as draft July 14, 2023 14:09
@richtja richtja linked an issue Jul 17, 2023 that may be closed by this pull request
@richtja richtja marked this pull request as ready for review July 17, 2023 12:11
Copy link
Contributor

@clebergnu clebergnu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @richtja ,

This LGTM, but it'd be great to also check for the exit code (AVOCADO_JOB_INTERRUPTED = 0x0008) in the selftests.

@richtja
Copy link
Contributor Author

richtja commented Jul 18, 2023

Hi @richtja ,

This LGTM, but it'd be great to also check for the exit code (AVOCADO_JOB_INTERRUPTED = 0x0008) in the selftests.

Sure thing, I will update that. Thanks for your review.

This will remove unsystematic timeout inside avocado-instrumented
runner. This timeout has been set to 24 hours and users haven't had a
way how to change it. Because we solved problems with
`task.timeout.running` in avocado-framework#5383 and `job-timeout` in avocado-framework#5295 this default
timeout is not needed anymore. After this change, the users will have
more power over timeouts and will be able to run instrumented tests
longer than 24 hours.

Reference: avocado-framework#5394
Signed-off-by: Jan Richter <[email protected]>
@richtja
Copy link
Contributor Author

richtja commented Aug 28, 2023

Hi @clebergnu I added the exit code check. Please take a look.

@richtja richtja requested a review from clebergnu August 28, 2023 14:13
@clebergnu
Copy link
Contributor

/packit copr-build

Copy link
Contributor

@clebergnu clebergnu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@clebergnu clebergnu merged commit 096da22 into avocado-framework:master Oct 5, 2023
58 checks passed
@richtja richtja deleted the default_timeout_fix branch October 9, 2023 08:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Avocado timeouts epic Remove runners own timeouts.
2 participants