[api-docs] raise memory limit again #107065
Merged
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
spalger
added
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
spalger
commented
Jul 28, 2021
brianseeders
approved these changes
Jul 28, 2021
spalger
added
the
auto-backport
💚 Build SucceededMetrics [docs]
To update your PR or re-run it, just comment with: |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jul 28, 2021
* [api-docs] raise memory limit again * update buildkite script too Co-authored-by: spalger <[email protected]>
💔 Backport failed
Successful backport PRs will be merged automatically after passing CI. To backport manually run: |
spalger
pushed a commit
to spalger/kibana
that referenced
this pull request
Jul 28, 2021
* [api-docs] raise memory limit again * update buildkite script too Co-authored-by: spalger <[email protected]> # Conflicts: # test/scripts/jenkins_baseline.sh
spalger
pushed a commit
that referenced
this pull request
Jul 28, 2021
* [api-docs] raise memory limit again * update buildkite script too Co-authored-by: spalger <[email protected]> # Conflicts: # test/scripts/jenkins_baseline.sh
kibanamachine
added a commit
that referenced
this pull request
Jul 28, 2021
* [api-docs] raise memory limit again * update buildkite script too Co-authored-by: spalger <[email protected]> Co-authored-by: Spencer <[email protected]> Co-authored-by: spalger <[email protected]>
streamich
pushed a commit
to vadimkibana/kibana
that referenced
this pull request
Aug 8, 2021
* [api-docs] raise memory limit again * update buildkite script too Co-authored-by: spalger <[email protected]>
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.
In #106735 I raised the memory limit of
node scripts/build_api_docsfor PRs and hourly jobs, but forgot that baseline jobs use a different script. This PR updates the memory limit in both places because looking at the results it seems that raising the limit to 8000 helped, but didn't eliminate OOM issues. The numbers on PRs look really good, with only one failure in a PR which ran after the memory limit was increased:(only includes successful jobs, x-axis is based on the time when the baseline jobs used completed, the yellow line shows where we merged the memory limit increase)
The results of baseline and hourly jobs looks similar:
