Use public pools for virtual builds #122
Closed
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
|
Ignore the CircleCI failures, they will go away once #120 is merged. |
|
This doesn't seem to work well, for some reason the connection attempts to 127.x.x.x fail: 27: 2019-06-05 21:41:11.648 | INFO | infra.proc:ccall:10 - ./client --host=127.39.200.128 --port=59713 --ca=0.pem startnetwork CircleCI does not suffer from this, so I will transfer the coverage build to the public CI, and add the SAN build either as a separate CircleCI job, or attach it to the public CI directly. |
olgavrou
approved these changes
Jun 6, 2019
jumaffre
approved these changes
Jun 6, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Public pools + containers are unfortunately very slow in Pipelines, but this frees up scarce SGX executor resources, so I think it's worth doing.