Skip to content

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

Closed

Conversation

wagnermaciel
Copy link
Contributor

@wagnermaciel wagnermaciel commented Apr 24, 2020

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

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.

@wagnermaciel wagnermaciel marked this pull request as ready for review April 28, 2020 23:07
@AndrewKushnir AndrewKushnir added the area: dev-infra Issues related to Angular's own dev infra (build, test, CI, releasing) label Apr 29, 2020
@ngbot ngbot bot added this to the needsTriage milestone Apr 29, 2020
Copy link
Contributor

@IgorMinar IgorMinar left a 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.

@wagnermaciel
Copy link
Contributor Author

wagnermaciel commented May 7, 2020

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 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.

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.

@wagnermaciel wagnermaciel force-pushed the redo-dev-infra-benchmarking branch 2 times, most recently from 5d7d209 to 3ea9584 Compare May 7, 2020 17:08
@wagnermaciel wagnermaciel force-pushed the redo-dev-infra-benchmarking branch from 857d98f to 96ddbc9 Compare May 8, 2020 22:31
@wagnermaciel wagnermaciel force-pushed the redo-dev-infra-benchmarking branch 2 times, most recently from 45fe6e4 to f1e5878 Compare May 11, 2020 18:47
Copy link
Member

@devversion devversion left a 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.

@wagnermaciel wagnermaciel requested review from IgorMinar and removed request for kara May 12, 2020 17:15
@wagnermaciel wagnermaciel force-pushed the redo-dev-infra-benchmarking branch 3 times, most recently from ee83640 to f78059a Compare May 15, 2020 18:23
Copy link
Contributor

@kyliau kyliau left a 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

Copy link
Contributor

@mhevery mhevery left a 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

@ngbot ngbot bot added the action: merge The PR is ready for merge by the caretaker label Jun 1, 2020
@wagnermaciel
Copy link
Contributor Author

This has a passing presubmit
https://tap.corp.google.com/ui#id=OCL:312733720:BASE:314181500:1591040024284:2b3c7ff4

The status isn't updating due to a rate limit error. This should be good to merge.

@wagnermaciel wagnermaciel force-pushed the redo-dev-infra-benchmarking branch from 8d9d51a to b19436a Compare June 2, 2020 18:49
@wagnermaciel
Copy link
Contributor Author

wagnermaciel commented Jun 2, 2020

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
https://tap.corp.google.com/ui#id=OCL:312733720:BASE:314181500:1591040024284:2b3c7ff4

Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@wagnermaciel wagnermaciel added the target: patch This PR is targeted for the next patch release label Jun 2, 2020
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.
@wagnermaciel wagnermaciel force-pushed the redo-dev-infra-benchmarking branch from b19436a to 987fe29 Compare June 2, 2020 19:26
@atscott atscott removed the request for review from gkalpak June 3, 2020 20:11
@atscott atscott closed this in caa4ab3 Jun 3, 2020
atscott pushed a commit that referenced this pull request Jun 3, 2020
atscott pushed a commit that referenced this pull request Jun 3, 2020
atscott pushed a commit that referenced this pull request Jun 3, 2020
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
atscott pushed a commit that referenced this pull request Jun 3, 2020
atscott pushed a commit that referenced this pull request Jun 3, 2020
atscott pushed a commit that referenced this pull request Jun 3, 2020
atscott pushed a commit that referenced this pull request Jun 3, 2020
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
ngwattcos pushed a commit to ngwattcos/angular that referenced this pull request Jun 25, 2020
ngwattcos pushed a commit to ngwattcos/angular that referenced this pull request Jun 25, 2020
ngwattcos pushed a commit to ngwattcos/angular that referenced this pull request Jun 25, 2020
ngwattcos pushed a commit to ngwattcos/angular that referenced this pull request Jun 25, 2020
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
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jul 4, 2020
profanis pushed a commit to profanis/angular that referenced this pull request Sep 5, 2020
profanis pushed a commit to profanis/angular that referenced this pull request Sep 5, 2020
profanis pushed a commit to profanis/angular that referenced this pull request Sep 5, 2020
profanis pushed a commit to profanis/angular that referenced this pull request Sep 5, 2020
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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: dev-infra Issues related to Angular's own dev infra (build, test, CI, releasing) cla: yes merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants