Skip to content

build: run lint jobs even if tests fail - #5609

Closed
Trott wants to merge 2 commits into
nodejs:masterfrom
Trott:reviewable
Closed

Trott wants to merge 2 commits into
nodejs:masterfrom
Trott:reviewable

Conversation

@Trott

@Trott Trott commented Mar 8, 2016

Copy link
Copy Markdown
Member
  • Does make -j8 test (UNIX) or vcbuild test nosign (Windows) pass with
    this change (including linting)?
  • Is the commit message formatted according to [CONTRIBUTING.md][0]?
  • If this change fixes a bug (or a performance problem), is a regression
    test (or a benchmark) included?
  • Is a documentation update included (if this change modifies
    existing APIs, or introduces new ones)?

Description of change

Reviewable version of Option 3 from #5607. If tests fail, lint still runs. Recipe exits with error if any tests or lint tasks don't run without incident.

This is a proof-of-concept for a small change but the small change has potentially enormous consequences. So, you know, don't merge casually. Added in progress label to try to make that clear.

@Trott Trott added wip Issues and PRs that are still a work in progress. build Issues and PRs related to Node.js builds or CI infrastructure. test Issues and PRs related to Node.js core tests and test infrastructure. labels Mar 8, 2016
@Trott

Trott commented Mar 8, 2016

Copy link
Copy Markdown
Member Author

CI, although i don't think this make-task is run on CI, but you know, just in case: https://ci.nodejs.org/job/node-test-commit/2494/

@Fishrock123

Copy link
Copy Markdown
Contributor

This looks fine to me, maybe @nodejs/ctc or @nodejs/build could comment?

@orangemocha

Copy link
Copy Markdown
Contributor

The code change LGTM per se, though I have not reviewed the merits of why this should be done (#5607)

@jbergstroem

Copy link
Copy Markdown
Member

I personally don't like this style and would prefer splitting them but can understand the rationale. I'm -0.

Comment thread Makefile Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Are these spaces? Need to be a tab.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Whoops! Rebased and changed to tabs.

@ofrobots

Copy link
Copy Markdown
Contributor

I would also prefer if the lint check was split out from the test and added as a prerequisite. I personally don't care about running lint while I am hacking at stuff, so I would like to be able to run the tests without the lint; it would be good if there was a target I could use to do that.

@Trott

Trott commented Mar 14, 2016

Copy link
Copy Markdown
Member Author

This doesn't seem like it's going to get consensus any time soon so I'm going to go ahead and close it. In theory, I do like the idea of separating the lint job from the test job entirely. In practice, I think people will just forget to lint and then we won't catch stuff until CI runs. So I'm not inclined to make that change myself. (But I wouldn't stop someone else who wanted to make it and could get consensus on it.)

@Trott Trott closed this Mar 14, 2016
@jbergstroem

Copy link
Copy Markdown
Member

@Trott we could always replace all references to make test with make lint test?

@Trott
Trott deleted the reviewable branch January 13, 2022 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Issues and PRs related to Node.js builds or CI infrastructure. test Issues and PRs related to Node.js core tests and test infrastructure. wip Issues and PRs that are still a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants