-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
meta: travis: start slower jobs first #27205
Conversation
One thing I have noticed is that the way staging works if any of the first stage jobs fail (e.g. commit message lint or linter) then the second stage isn't run (i.e. no tests are run). On the one hand having the linting done in the first stage returns results quicker, but maybe we can move linting into the test stage so all linting and tests are attempted (assuming the code compiles)? |
So that |
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.
nit: when squashing please reword the first commit (something like "run compilation jobs first").
even though jobs can run in parallel they start in declaration order * this patch makes "compiles >> no lint" in terms of precedence PR-URL: nodejs#27205 Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
aba17c6
to
f3b5cc0
Compare
even though jobs can run in parallel they start in declaration order
/CC @nodejs/build-files @nodejs/testing
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes