-
Notifications
You must be signed in to change notification settings - Fork 562
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
tests: set to 10 minutes the kill timeout for tests failing on slow boards #10664
tests: set to 10 minutes the kill timeout for tests failing on slow boards #10664
Conversation
Some of these tests are failing on pi2 and pi3 in the lab with kill timeout. Some boards are getting slow and the idea is to move from 5m to 10m to avoid those issues. The affected tests are the ones that run on ubuntu core.
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.
LGTM
Codecov Report
@@ Coverage Diff @@
## master #10664 +/- ##
==========================================
- Coverage 80.71% 78.32% -2.40%
==========================================
Files 727 882 +155
Lines 58158 99360 +41202
==========================================
+ Hits 46940 77819 +30879
- Misses 7544 16649 +9105
- Partials 3674 4892 +1218
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
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.
Looks fine, just one question inline.
@@ -3,7 +3,7 @@ summary: "Check that refresh-modes works" | |||
# takes >1.5min to run | |||
backends: [-autopkgtest] | |||
|
|||
kill-timeout: 12m | |||
kill-timeout: 10m |
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.
(nitpick) here the time decreases by 2min, is that intentional?
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.
Yes, see the bottom of PR desc: The test services-refresh-mode initially was in 5 minutes, then moved to 12 but when tested with 10m it works fine.
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.
lgtm
Test failures are unrealted, @mvo5 can you merge it? |
Some of these tests are failing on pi2 and pi3 in the lab with kill
timeout.
Some boards are getting slow and the idea is to move from 5m to 10m to
avoid those issues.
The affected tests are the ones that run on ubuntu core.
The test services-refresh-mode initially was in 5 minutes, then moved to 12 but when tested with 10m it works fine.