This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Chore travis split unit #16292
Merged
Chore travis split unit #16292
Conversation
This file contains hidden or 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
Narretz
force-pushed
the
chore-travis-split-unit
branch
7 times, most recently
from
993c915 to
9e8ca59
Compare
Narretz
force-pushed
the
chore-travis-split-unit
branch
from
dd0830c to
694dc3e
Compare
"unit-core" consists of code+jqlite, module test, and promise A+ tests. "unit-jquery" is code+jquery "docs-app" includes unit and e2e tests Splitting the unit tests into more than one job makes it faster to rerun jobs that fail because Safari or Edge cannot complete the suite, which seemingly happens on random.
Narretz
force-pushed
the
chore-travis-split-unit
branch
from
694dc3e to
58b2222
Compare
Narretz
added a commit
to Narretz/angular.js
that referenced
this pull request
Oct 25, 2017
"unit-core" consists of code+jqlite, module test, and promise A+ tests. "unit-jquery" is code+jquery "docs-app" includes unit and e2e tests Splitting the unit tests into more than one job makes it faster to rerun jobs that fail because Safari or Edge cannot complete the suite, which seemingly happens on random. Closes angular#16292
Narretz
added a commit
that referenced
this pull request
Oct 25, 2017
"unit-core" consists of code+jqlite, module test, and promise A+ tests. "unit-jquery" is code+jquery "docs-app" includes unit and e2e tests Splitting the unit tests into more than one job makes it faster to rerun jobs that fail because Safari or Edge cannot complete the suite, which seemingly happens on random. Closes #16292
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change?
Please check if the PR fulfills these requirements
Other information: