-
Notifications
You must be signed in to change notification settings - Fork 8.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[7.x] chore(NA): moving @elastic/datemath into bazel (#94665) #96105
Merged
+368
−60
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
* chore(NA): majority of the changes needed to build elastic-datemath with bazel * chore(NA): add missing bits on elastic-datemath package * chore(NA): add missing build and watch scripts * chore(NA): remove build scripts for elastic datemah * chore(NA): remove typo from build baze production projects logs * chore(NA): force install on CI * chore(NA): introduce custom preserve symlinks resolver for jest * chore(NA): update jest integration snapshot * chore(NA): fix build for bazel packages * chore(NA): correctly copy bazel built packages into final distributable build * chore(NA): update kbn pm dist * chore(NA): experimental new logic to handle bazel yarn rule rerun using yarn-integrity file * chore(NA): update snapshots * refact(NA): ensure yarn integrity exists into two methods * chore(NA): fix ts error * chore(NA): update snapshots * chore(NA): update elastic-datemath build file to include ts_project rule * chore(NA): update basic optimization test snapshots * chore(NA): merge and solve conflicts cherry-pick from elastic#96066 * chore(NA): update package.json and yarn.lock file * chore(NA): update bazel/bin into bazel-bin on kbn-pm build bazel packages Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> # Conflicts: # package.json
💛 Build succeeded, but was flaky
Test FailuresKibana Pipeline / general / Chrome UI Functional Tests.test/functional/apps/dashboard/empty_dashboard·ts.dashboard app using current data empty dashboard should add new visualization from dashboardStandard Out
Stack Trace
Kibana Pipeline / general / Chrome UI Functional Tests.test/functional/apps/dashboard/empty_dashboard·ts.dashboard app using current data empty dashboard "after all" hook for "should add new visualization from dashboard"Standard Out
Stack Trace
Metrics [docs]
To update your PR or re-run it, just comment with: |
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.
Backports the following commits to 7.x: