FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

test: skip doctool tests when js-yaml is missing by addaleax · Pull Request #7218 · nodejs/node · GitHub

/ node Public

test: skip doctool tests when js-yaml is missing - #7218

Merged
addaleax merged 1 commit into
nodejs:masterfrom
addaleax:skip-doctool-tests-without-eslint
Jul 6, 2016
Merged

test: skip doctool tests when js-yaml is missing#7218
addaleax merged 1 commit into
nodejs:masterfrom
addaleax:skip-doctool-tests-without-eslint

Conversation

addaleax commented Jun 8, 2016
edited
Loading

Copy link
Copy Markdown
Member
Checklist
  • make -j4 test (UNIX) or vcbuild test nosign (Windows) passes
  • the commit message follows commit guidelines
Affected core subsystem(s)

test

Description of change

Skip the doctool tests when js-yaml, which is currently require()d from the eslint source tree, is missing. This can happen, for example, because eslint is not included in the release source tarballs.

Fixes: #7201
Ref (introduced in): #6495

CI: https://ci.nodejs.org/job/node-test-commit/3692/

addaleax added doc Issues and PRs related to the documentations. test Issues and PRs related to the tests. tools Issues and PRs related to the tools directory. labels Jun 8, 2016

Copy link
Copy Markdown
Contributor

LGTM, but we should eventually find a solution. What's js-yaml used for, by the way? Just the "added" comments?

addaleax commented Jun 8, 2016

Copy link
Copy Markdown
Member Author

+1 – it’s one of the things that have led me to open #6999. And yeah, exactly that… I don’t know if it would have been my first choice but I carried it over from the original #3867 because I didn’t see much speaking against it.

Copy link
Copy Markdown
Contributor

Hmmm, when will this be skipped? Only from the tarball, not on the CI?

Copy link
Copy Markdown
Member Author

@Fishrock123 yes, only the tarball.

There’s also #7290 that addresses the same problem by actually adding the dependencies, and I don’t have any too strong feelings, which is why I didn’t merge this yet.

Copy link
Copy Markdown
Contributor

I personally prefer this approach.

addaleax commented Jul 5, 2016

Copy link
Copy Markdown
Member Author

@thefourtheye Would you mind if I landed this? That doesn’t need to be the end of discussion, but it might be nice to have make test from tarballs working again.

Copy link
Copy Markdown
Contributor

No problem. Working tarball is important. LGTM.

Skip the doctool tests when js-yaml, which is currently `require()`d
from the eslint source tree, is missing. This can happen, for example,
because eslint is not included in the release source tarballs.

Fixes: nodejs#7201
Ref: nodejs#6495
PR-URL: nodejs#7218
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
addaleax force-pushed the skip-doctool-tests-without-eslint branch from 77f3034 to af273b5 Compare July 6, 2016 10:41

addaleax commented Jul 6, 2016

Copy link
Copy Markdown
Member Author

rebased, CI again just to be sure: https://ci.nodejs.org/job/node-test-commit/3991/

addaleax merged commit af273b5 into nodejs:master Jul 6, 2016
addaleax deleted the skip-doctool-tests-without-eslint branch July 6, 2016 12:27

Copy link
Copy Markdown
Contributor

@addaleax lts? If so can you backport? Not landing cleanly

(thanks for being so responsive today!)

evanlucas pushed a commit that referenced this pull request Jul 12, 2016
Skip the doctool tests when js-yaml, which is currently `require()`d
from the eslint source tree, is missing. This can happen, for example,
because eslint is not included in the release source tarballs.

Fixes: #7201
Ref: #6495
PR-URL: #7218
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
addaleax added a commit to addaleax/node that referenced this pull request Jul 12, 2016
Skip the doctool tests when js-yaml, which is currently `require()`d
from the eslint source tree, is missing. This can happen, for example,
because eslint is not included in the release source tarballs.

Fixes: nodejs#7201
Ref: nodejs#6495
PR-URL: nodejs#7218
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
MylesBorins pushed a commit that referenced this pull request Jul 12, 2016
Skip the doctool tests when js-yaml, which is currently `require()`d
from the eslint source tree, is missing. This can happen, for example,
because eslint is not included in the release source tarballs.

Fixes: #7201
Ref: #6495
PR-URL: #7218
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
MylesBorins pushed a commit that referenced this pull request Jul 12, 2016
Skip the doctool tests when js-yaml, which is currently `require()`d
from the eslint source tree, is missing. This can happen, for example,
because eslint is not included in the release source tarballs.

Fixes: #7201
Ref: #6495
PR-URL: #7218
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
MylesBorins mentioned this pull request Jul 12, 2016
MylesBorins pushed a commit that referenced this pull request Jul 14, 2016
Skip the doctool tests when js-yaml, which is currently `require()`d
from the eslint source tree, is missing. This can happen, for example,
because eslint is not included in the release source tarballs.

Fixes: #7201
Ref: #6495
PR-URL: #7218
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
MylesBorins pushed a commit that referenced this pull request Jul 14, 2016
Skip the doctool tests when js-yaml, which is currently `require()`d
from the eslint source tree, is missing. This can happen, for example,
because eslint is not included in the release source tarballs.

Fixes: #7201
Ref: #6495
PR-URL: #7218
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com>
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Issues and PRs related to the documentations. test Issues and PRs related to the tests. tools Issues and PRs related to the tools directory.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants


Back | FazBrowse Home | New Git URL