build(ivy): fix benchmarks #26601
Closed
build(ivy): fix benchmarks #26601
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
kara
added
type: bug/fix
area: build & ci
mhevery
approved these changes
Oct 19, 2018
kara
added
action: merge
IgorMinar
approved these changes
Oct 19, 2018
alxhub
pushed a commit
that referenced
this pull request
Oct 22, 2018
sculove
pushed a commit
to sculove/angular
that referenced
this pull request
Nov 2, 2018
FrederikSchlemmer
pushed a commit
to FrederikSchlemmer/angular
that referenced
this pull request
Jan 3, 2019
|
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.
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.
Our benchmarks weren't running properly because Benchpress now uses performance mark events and we hadn't turned on "user timing" events in our protractor config. This small PR should fix that.