Repository navigation
fix: wait out apt at start-up; count gateway 502s as gateway failures - #26
Merged
Merged
Conversation
Six full-run-3 installs failed on a dpkg lock held by an apt process the image started. A 502 outage counted as finished trials and wasn't rerun. Also records the analysis behind the next experiments.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
setup()waits (up to 120 s, plain sh and /proc) for apt/dpkg the image left running. Six full-run-3 installs failed on that lock.InternalServerError(gateway 502) now counts as a gateway failure inrun_full.sh resume,score.pyandexport_trials.py; a 502 outage on 10-12 was counted as finished trials.