Repository navigation
Travis linter false-negatives for commit message checks #23737
Copy link
Copy link
Closed
Labels
buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.metaIssues and PRs related to the general management of the project.Issues and PRs related to the general management of the project.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Description
Activity
- addedbuildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.
on Oct 18, 2018 Opened #23739 to stop linting...
- addedtestIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.metaIssues and PRs related to the general management of the project.Issues and PRs related to the general management of the project.flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.
on Oct 18, 2018 The original issue is that Travis was misidentifying the commits for a PR.
Rather than rely on Travis to work out which commits should be linted, #24030, #24076, #24093 changed the Travis linter to use GitHub's API to query for commits for the PR being tested so should now be consistent with the list of commits for a PR in the GitHub web UI.
- added a commit that references this issue
on Nov 6, 2018 - added a commit that references this issue
on Nov 6, 2018 - added a commit that references this issue
on Nov 15, 2018 - added a commit that references this issue
on Nov 29, 2018 - added 2 commits that reference this issue
on Nov 29, 2018
Metadata
Metadata
Assignees
Labels
buildIssues and PRs related to Node.js builds or CI infrastructure.Issues and PRs related to Node.js builds or CI infrastructure.flaky-testIssues and PRs involving tests that fail intermittently in CI.Issues and PRs involving tests that fail intermittently in CI.metaIssues and PRs related to the general management of the project.Issues and PRs related to the general management of the project.testIssues and PRs related to Node.js core tests and test infrastructure.Issues and PRs related to Node.js core tests and test infrastructure.
Saw this on two PRs today (#23512 and #22079), Travis is complaining that "subsystem is missing". In both cases commit message is following our guidelines and have a valid subsystem in their titles.