Skip to content

[CI] Frequent timeouts for XPackRestIT #48212

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.

Sign up for GitHub

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

Jump to bottom
Closed
mark-vieira opened this issue Oct 17, 2019 · 2 comments · Fixed by #48237
Closed

[CI] Frequent timeouts for XPackRestIT #48212

mark-vieira opened this issue Oct 17, 2019 · 2 comments · Fixed by #48237
Assignees
@alpar-t
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@mark-vieira
Copy link
Contributor

mark-vieira commented Oct 17, 2019 •
edited
Loading

We have a decent number of builds failing due to the XPackRestIT suite timing out.

I'm thinking this might just be a case of this suite growing bigger and bigger and simply getting too close to the default suite timeout of 20 minutes. As you can tell from this build the suite took over 19m during a successful run. Perhaps it makes sense to bump the suite timeout for this test or break it up, depending on how easy that might be.
@mark-vieira mark-vieira added :Delivery/Build Build or test infrastructure >test-failure Triaged test failures from CI labels Oct 17, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (:Core/Infra/Build)

@alpar-t alpar-t mentioned this issue Oct 18, 2019
Closed
@alpar-t
Copy link
Contributor

alpar-t commented Oct 18, 2019

It would be better to have a lot of tolerance at the suite level and tighter timeouts on the individual methods ?

This would be solved by #47793 in a better way by making the timeout dependent on the number of individual tests.

I'we been thinking about splitting these large tests for a while so I added #48229 to have it in writing.

@alpar-t alpar-t self-assigned this Oct 18, 2019
alpar-t added a commit to alpar-t/elasticsearch that referenced this issue Oct 18, 2019
@alpar-t
Increase timeout for yml tests
ebd156b 
Some of these are larger than what can complete in the regular timeout.

Closes elastic#48212
@alpar-t alpar-t mentioned this issue Oct 18, 2019
Merged
mark-vieira pushed a commit that referenced this issue Oct 18, 2019
@alpar-t @mark-vieira
Increase timeout for yml tests (#48237)
7b1d50a 
Some of these are larger than what can complete in the regular timeout.

Closes #48212
mark-vieira pushed a commit that referenced this issue Oct 18, 2019
@alpar-t @mark-vieira
Increase timeout for yml tests (#48237)
cc26e30 
Some of these are larger than what can complete in the regular timeout.

Closes #48212
mark-vieira pushed a commit that referenced this issue Oct 18, 2019
@alpar-t @mark-vieira
Increase timeout for yml tests (#48237)
fd1a78b 
Some of these are larger than what can complete in the regular timeout.

Closes #48212
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alpar-t alpar-t

Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Increase timeout for yml tests alpar-t/elasticsearch
3 participants
@alpar-t @mark-vieira @elasticmachine