[CI] Delete node_modules in between bootstrap attempts#117588
[CI] Delete node_modules in between bootstrap attempts#117588brianseeders merged 1 commit intoelastic:mainfrom
Conversation
|
Pinging @elastic/kibana-operations (Team:Operations) |
|
|
||
| # Most bootstrap failures will result in a problem inside node_modules that does not get fixed on the next bootstrap | ||
| # So, we should just delete node_modules in between attempts | ||
| rm -rf node_modules |
There was a problem hiding this comment.
We might want to consider yarn kbn clean as it also resets things like Bazel if there were an issue there. But deleting node_modules should accomplish what we're looking to resolve there without possible side-effects clean might have.
There was a problem hiding this comment.
Though, if we used clean we would have to re-extract the plugins. So, nevermind.
There was a problem hiding this comment.
Yeah, I really hope that there's never a time where Bazel starts to handle failures like yarn does
💚 Build Succeeded
Metrics [docs]
To update your PR or re-run it, just comment with: |
…ink-to-kibana-app * 'main' of github.com:elastic/kibana: (290 commits) [Connectors][ServiceNow] Remove SN flags (elastic#117511) [ML] Functional tests - stabilize and re-enable feature importance tests (elastic#117503) [RAC] Disable the actions button if the user has inadequate privileges (elastic#117488) [Visualize] [xyChart] filter labels by default (elastic#117288) Fix warning when setting description to undefined (elastic#117338) [build] Set monitoring.ui.container.elasticsearch.enabled for all containers (elastic#115087) fix types [Alerting] UX fixes for execution duration chart (elastic#117193) [CI] Delete node_modules in between bootstrap attempts (elastic#117588) Flaky test fixes (elastic#117028) [Security Solution] [Sourcerer] [Feature Branch] Update to use Kibana Data Views (elastic#114806) [ML] Hide anomaly entity filter button tooltips when clicked (elastic#117493) adjust the synthetics journey type (elastic#117316) Refines hasAnyData check for alerts (elastic#117499) [Fleet] Default to APM tutorial (elastic#117421) [Maps] update docs for index pattern -> data view rename (elastic#117400) [Logs UI][Metrics UI] Remove deprecated config fields from APIs and SavedObjects (elastic#116821) [Fleet] Fix agent logs not reading query from URL (elastic#117286) Fixing Failing test: Chrome X-Pack UI Functional Tests.x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/alert_create_flyout·ts - Actions and Triggers app create alert should successfully test valid es_query alert (elastic#114917) [Metrics UI] Add docs link to redundant groupBy detection (elastic#116822) ... # Conflicts: # x-pack/plugins/reporting/public/management/__snapshots__/report_listing.test.tsx.snap # x-pack/plugins/reporting/public/shared_imports.ts # x-pack/plugins/reporting/server/routes/management/jobs.ts
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
1 similar comment
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
When bootstrap fails, it usually results in a problem inside
node_modulesthat is not corrected on the next bootstrap. This is likely because ofpostinstallscripts that don't run.See here for an example: https://buildkite.com/elastic/kibana-on-merge/builds/7291#37f2ecc1-4dc5-4789-bac2-99e7dac1d560
We have lots of random failures in CI because of this. Deleting
node_modulesbefore the retry should fix the problem.