[CI] Run intake workspaces in-memory to reduce run time #66827
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
brianseeders
added
Feature:CI
jbudz
approved these changes
May 15, 2020
|
@elasticmachine merge upstream |
…o intake-in-memory
|
@elasticmachine merge upstream |
|
(jenkins upgrade required killing all jobs) |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
|
@elasticmachine merge upstream |
|
Pinging @elastic/kibana-operations (Team:Operations) |
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.
This makes Jest tests much faster.
This PR will be cleaner once #67413 is merged.
Edit: It looks like there's not actually enough memory on this size of server to put the workspace in memory. I thought there was a reason we didn't do this before.