Reduce time for reproducibility and DGI save/load tests #1721
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.
The time for the 3.x pytest testing step seems to be bimodal at the moment: usually around 18 minutes, but sometimes hitting the 30 minute timeout. This may be due to the agent running out of burst credits, and thus running slower.
This causes problems both with the time it takes for the build to run and with the build failing due to the timeout. Cutting the test times will make development easier.
In https://buildkite.com/stellar/stellargraph-public/builds/5012, the 3.7 and 3.8 steps take about 30 minutes, but get in just under the timeout. Based on the JUnit XML files there, the slowest tests are:
3.7:
3.8:
Clearly saving/loading a HinSAGE Deep Graph Infomax model is extremely slow, as are all of the reproducibility tests. This PR removes the HinSAGE DGI test save-load test, and reduces the repeats for the reproducibility ones to just two: the reference model and then one repeat. (The reproducibility tests are quite flaky at the moment, so it's kinda a waste to spend a lot of CPU time on them.)