[nexus] mark schema tests as heavy, increase timeout for one of them #4832
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On my Linux machine, when running the tests in test_all, I'm starting to see
integration_tests::schema::nexus_applies_update_on_boot
fail because of a 60s timeout waiting for nexus to start. The failure is caused
due to contention -- the logs just seem to indicate each schema version taking
5-15 seconds to apply.
To address this, do two things:
In the future, we may want to do something more clever like breaking this test
up into several smaller ones.
Error message:
Logs: https://gist.github.com/sunshowers/39ee99badc5f75c2a3154ea602aa95aa