This repository has been archived by the owner on Jan 30, 2020. It is now read-only.
fix(tests): plethora of fixes to functional tests #537
Conversation
This file contains 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
- remove update-ca-certificates from node start, dramatically reducing container spin-up time - removing time.Sleep when spinning up a node; instead, poll until it looks like the container is fully booted - cleaning up network interfaces more thoroughly between tests, preventing a race where one test failure will cause a cascading failure in subsequent tests - copies /etc/nsswitch.conf into container to ensure users are available during startup (in the non-container world this is handled by initrd)
|
this makes me so happy The fact that it's taken me all week to track down all the bugz makes me sad. |
|
|
bcwaldon
added a commit
that referenced
this pull request
Jun 16, 2014
fix(tests): plethora of fixes to functional tests
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
container spin-up time
it looks like the container is fully booted
preventing a race where one test failure will cause a cascading
failure in subsequent tests
during startup (in the non-container world this is handled by initrd)