-
Notifications
You must be signed in to change notification settings - Fork 26.3k
Redo dev infra benchmarking #36800
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
Redo dev infra benchmarking #36800
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey Wagner!
What's going on with this PR? Can you please provide a bit more context? Thanks
Side-note: the current commit messages just state that these are reverts of reverts which is a bit confusing. But let's sort out what you are trying to do here before we worry about the commit messages.
Hi Igor, For context, these changes were already submitted once in PR #36721. They were reverted by PR #36798 when @AndrewKushnir noticed that the updated files in the modules folder refer to the dev-infra package that we do not sync in g3, which would likely have caused build failures. I am not sure why NG Bot indicated (in “g3 status”) that the first PR wouldn't affect g3, when in fact it would have. The difference between this PR and the previous one is that it has been g3synced using CL #309492386's copy.bara.sky configuration. This change syncs The commit messages (while they are confusing) reflect the correct history of these changes. I am OK with changing them if we would prefer to have clarity over historical accuracy in this case. I have added this to the PR description and if you would like I can also add this to the body of a commit message. |
5d7d209
to
3ea9584
Compare
857d98f
to
96ddbc9
Compare
45fe6e4
to
f1e5878
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. A few minor comments from my side.
dev-infra/benchmark/component_benchmark/component_benchmark.bzl
Outdated
Show resolved
Hide resolved
ee83640
to
f78059a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for language service
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM for zone.js
This has a passing presubmit The status isn't updating due to a rate limit error. This should be good to merge. |
…ark' via dev_infra (angular#36434)" (angular#36798)" This reverts commit ad8c4cd.
…age (angular#36434)" (angular#36798)" This reverts commit f5ff206.
… show PoC (angular#36434)" (angular#36798)" This reverts commit 90a2796.
8d9d51a
to
b19436a
Compare
Currently rebasing to try and get around GitHub's status limit. Code should still be safe to merge, I am just trying to update the status here. Update: Rebasing did not allow me to update the status. Still getting rate limited by GitHub. To reiterate, this PR has a passing presubmit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Rename bazel workspace from npm_dev_infra to npm_angular_dev_infra_private to make it clear that this package is private to angular. Change driver-utilities module_name to match the new bazel workspace name. Correct a comment by rewording it from "deployed version" to "published version". Fix merge conflicts in tmpl-package.json Make "//packages/bazel/src:esm5.bzl" replacement more generalized so that importing from "//packages/bazel" works. Deleted "dev_infra/*" path from modules/benchmarks tsconfig. Moved //dev-infra/benchmark/browsers to //dev-infra/browsers.
b19436a
to
987fe29
Compare
Rename bazel workspace from npm_dev_infra to npm_angular_dev_infra_private to make it clear that this package is private to angular. Change driver-utilities module_name to match the new bazel workspace name. Correct a comment by rewording it from "deployed version" to "published version". Fix merge conflicts in tmpl-package.json Make "//packages/bazel/src:esm5.bzl" replacement more generalized so that importing from "//packages/bazel" works. Deleted "dev_infra/*" path from modules/benchmarks tsconfig. Moved //dev-infra/benchmark/browsers to //dev-infra/browsers. PR Close #36800
Rename bazel workspace from npm_dev_infra to npm_angular_dev_infra_private to make it clear that this package is private to angular. Change driver-utilities module_name to match the new bazel workspace name. Correct a comment by rewording it from "deployed version" to "published version". Fix merge conflicts in tmpl-package.json Make "//packages/bazel/src:esm5.bzl" replacement more generalized so that importing from "//packages/bazel" works. Deleted "dev_infra/*" path from modules/benchmarks tsconfig. Moved //dev-infra/benchmark/browsers to //dev-infra/browsers. PR Close #36800
…ark' via dev_infra (angular#36434)" (angular#36798)" (angular#36800) This reverts commit ad8c4cd. PR Close angular#36800
…age (angular#36434)" (angular#36798)" (angular#36800) This reverts commit f5ff206. PR Close angular#36800
… show PoC (angular#36434)" (angular#36798)" (angular#36800) This reverts commit 90a2796. PR Close angular#36800
Rename bazel workspace from npm_dev_infra to npm_angular_dev_infra_private to make it clear that this package is private to angular. Change driver-utilities module_name to match the new bazel workspace name. Correct a comment by rewording it from "deployed version" to "published version". Fix merge conflicts in tmpl-package.json Make "//packages/bazel/src:esm5.bzl" replacement more generalized so that importing from "//packages/bazel" works. Deleted "dev_infra/*" path from modules/benchmarks tsconfig. Moved //dev-infra/benchmark/browsers to //dev-infra/browsers. PR Close angular#36800
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
…ark' via dev_infra (angular#36434)" (angular#36798)" (angular#36800) This reverts commit ad8c4cd. PR Close angular#36800
…age (angular#36434)" (angular#36798)" (angular#36800) This reverts commit f5ff206. PR Close angular#36800
… show PoC (angular#36434)" (angular#36798)" (angular#36800) This reverts commit 90a2796. PR Close angular#36800
Rename bazel workspace from npm_dev_infra to npm_angular_dev_infra_private to make it clear that this package is private to angular. Change driver-utilities module_name to match the new bazel workspace name. Correct a comment by rewording it from "deployed version" to "published version". Fix merge conflicts in tmpl-package.json Make "//packages/bazel/src:esm5.bzl" replacement more generalized so that importing from "//packages/bazel" works. Deleted "dev_infra/*" path from modules/benchmarks tsconfig. Moved //dev-infra/benchmark/browsers to //dev-infra/browsers. PR Close angular#36800
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Context
These changes were already submitted once in PR #36721. They were reverted by PR #36798 when @AndrewKushnir noticed that the updated files in the modules folder refer to the dev-infra package that we do not sync in g3, which would likely have caused build failures. I am not sure why NG Bot indicated (in “g3 status”) that the first PR wouldn't affect g3, when in fact it would have.
The difference between this PR and the previous one is that it has been g3synced using CL #309492386's copy.bara.sky configuration. This change syncs
dev-infra/benchmark/driver-utilities/**
into g3.The commit messages (while they are confusing) reflect the correct history of these changes. I am OK with changing them if we would prefer to have clarity over historical accuracy in this case.