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
build: disambiguate rollup progress message #23318
Closed
Closed
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
All our package labels are `npm_package` so the bazel build reports a bunch of identical actions running, like ``` Angular Packaging: rolling up npm_package; 31s darwin-sandbox Angular Packaging: rolling up npm_package; 30s darwin-sandbox Angular Packaging: rolling up npm_package; 29s darwin-sandbox Angular Packaging: rolling up npm_package; 27s darwin-sandbox Angular Packaging: rolling up npm_package; 26s darwin-sandbox Angular Packaging: rolling up npm_package; 23s darwin-sandbox Angular Packaging: rolling up npm_package; 19s darwin-sandbox Angular Packaging: rolling up npm_package; 11s darwin-sandbox ```
alexeagle
added
action: merge
The PR is ready for merge by the caretaker
target: major
This PR is targeted for the next major release
area: bazel
Issues related to the published `@angular/bazel` build rules
labels
Apr 11, 2018
You can preview fb4513c at https://pr23318-fb4513c.ngbuilds.io/. |
IgorMinar
approved these changes
Apr 11, 2018
wKoza
pushed a commit
to wKoza/angular
that referenced
this pull request
Apr 13, 2018
All our package labels are `npm_package` so the bazel build reports a bunch of identical actions running, like ``` Angular Packaging: rolling up npm_package; 31s darwin-sandbox Angular Packaging: rolling up npm_package; 30s darwin-sandbox Angular Packaging: rolling up npm_package; 29s darwin-sandbox Angular Packaging: rolling up npm_package; 27s darwin-sandbox Angular Packaging: rolling up npm_package; 26s darwin-sandbox Angular Packaging: rolling up npm_package; 23s darwin-sandbox Angular Packaging: rolling up npm_package; 19s darwin-sandbox Angular Packaging: rolling up npm_package; 11s darwin-sandbox ``` PR Close angular#23318
wKoza
pushed a commit
to wKoza/angular
that referenced
this pull request
Apr 13, 2018
All our package labels are `npm_package` so the bazel build reports a bunch of identical actions running, like ``` Angular Packaging: rolling up npm_package; 31s darwin-sandbox Angular Packaging: rolling up npm_package; 30s darwin-sandbox Angular Packaging: rolling up npm_package; 29s darwin-sandbox Angular Packaging: rolling up npm_package; 27s darwin-sandbox Angular Packaging: rolling up npm_package; 26s darwin-sandbox Angular Packaging: rolling up npm_package; 23s darwin-sandbox Angular Packaging: rolling up npm_package; 19s darwin-sandbox Angular Packaging: rolling up npm_package; 11s darwin-sandbox ``` PR Close angular#23318
wKoza
pushed a commit
to wKoza/angular
that referenced
this pull request
Apr 13, 2018
All our package labels are `npm_package` so the bazel build reports a bunch of identical actions running, like ``` Angular Packaging: rolling up npm_package; 31s darwin-sandbox Angular Packaging: rolling up npm_package; 30s darwin-sandbox Angular Packaging: rolling up npm_package; 29s darwin-sandbox Angular Packaging: rolling up npm_package; 27s darwin-sandbox Angular Packaging: rolling up npm_package; 26s darwin-sandbox Angular Packaging: rolling up npm_package; 23s darwin-sandbox Angular Packaging: rolling up npm_package; 19s darwin-sandbox Angular Packaging: rolling up npm_package; 11s darwin-sandbox ``` PR Close angular#23318
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. |
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: bazel
Issues related to the published `@angular/bazel` build rules
cla: yes
target: major
This PR is targeted for the next major release
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.
All our package labels are
npm_package
so the bazel build reports a bunch of identical actions running, like