Skip to content
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

test: do not use more command on Windows #11953

Closed
wants to merge 1 commit into from
Closed

test: do not use more command on Windows #11953

wants to merge 1 commit into from

Conversation

vsemozhetbyt
Copy link
Contributor

@vsemozhetbyt vsemozhetbyt commented Mar 21, 2017

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

test

Fixes: #11469

@nodejs-github-bot nodejs-github-bot added the test Issues and PRs related to the tests. label Mar 21, 2017
@vsemozhetbyt vsemozhetbyt added doc Issues and PRs related to the documentations. windows Issues and PRs related to the Windows platform. labels Mar 21, 2017
@vsemozhetbyt
Copy link
Contributor Author

@jasnell
Copy link
Member

jasnell commented Mar 21, 2017

@nodejs/platform-windows

Copy link
Member

@joaocgreis joaocgreis left a comment

Choose a reason for hiding this comment

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

LGTM

@joaocgreis
Copy link
Member

cc @nodejs/testing

@gibfahn
Copy link
Member

gibfahn commented Mar 21, 2017

Is cat included by default on windows machines? I know you get it through Git Bash, which we require, but I didn't think it came with CMD by default.

@vsemozhetbyt
Copy link
Contributor Author

vsemozhetbyt commented Mar 21, 2017

@gibfahn I don't think cat is included. I just thought the build requirements was a safe condition for it.

@joaocgreis
Copy link
Member

@gibfahn no, not by default. We already require Git Bash, tests already fail if the Unix tools are not installed, so I think it's better to make it consistent.

@vsemozhetbyt you have the same issue in Refs: and Fixes:, you can leave only the Fixes: line.

@gibfahn
Copy link
Member

gibfahn commented Mar 21, 2017

@vsemozhetbyt Yep, that was the context I hadn't seen.

I think it's fine to assume the developer will have cat.exe on the system due to it being included in Git Bash, the only issue is that the developer might not have the path to the Git command tools in their CMD path. I guess the answer is to document that you will need to add C:\Program Files\Git\usr\bin to your system path if it's not there already.

@vsemozhetbyt
Copy link
Contributor Author

@gibfahn It seems something like that is already present in the doc:

Basic Unix tools required for some tests, Git for Windows includes Git Bash and tools which can be included in the global PATH.

@seishun
Copy link
Contributor

seishun commented Mar 21, 2017

the only issue is that the developer might not have the path to the Git command tools in their CMD path

That's the same with other tests too.

Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@Trott Trott left a comment

Choose a reason for hiding this comment

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

LGTM. Happy to see stuff being removed from the common.js monolith!

vsemozhetbyt added a commit that referenced this pull request Mar 23, 2017
PR-URL: #11953
Fixes: #11469
Reviewed-By: João Reis <reis@janeasystems.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
@vsemozhetbyt
Copy link
Contributor Author

Landed in 2dff3a2

@vsemozhetbyt vsemozhetbyt deleted the more-to-cat branch March 23, 2017 03:57
MylesBorins pushed a commit that referenced this pull request Mar 28, 2017
PR-URL: #11953
Fixes: #11469
Reviewed-By: João Reis <reis@janeasystems.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
@MylesBorins MylesBorins mentioned this pull request Mar 28, 2017
@italoacasas italoacasas mentioned this pull request Apr 10, 2017
2 tasks
@MylesBorins
Copy link
Contributor

This is causing failures for OSX testing on v6.x. did not cherry-pick. LMK if it should land

@refack refack added the post-mortem Issues and PRs related to the post-mortem diagnostics of Node.js. label Apr 18, 2017
@refack
Copy link
Contributor

refack commented Apr 18, 2017

post-mortem

  1. I pro-uniformity (i.e. anti-disparity). (so I'm not suggesting we use the built in Windows type which is the equivalent to cat)
  2. I don't have cat in my Path, also adding ...\Git\usr\bin or any other unix tools folder, as it has some non-trivial side effects.
  3. I have no problem with special setup for building/testing node.

bottom-line

But in case changes like this are added I would like to ask for a quick failing sanity check to be added to run early to remind us if something in the environment is missing
/cc @nodejs/platform-windows

@refack
Copy link
Contributor

refack commented Apr 18, 2017

Such a test will also be a defacto documentation of what the following process is dependent on.

@gibfahn
Copy link
Member

gibfahn commented Apr 18, 2017

also adding ...\Git\usr\bin or any other unix tools folder, as it has some non-trivial side effects.

Out of interest, what side effects are those?

I would like to ask for a quick failing sanity check to be added to run early to remind us if something in the environment is missing

A test that just runs through all the tools test.py expects makes sense to me, and not just for Windows.

@benjamingr
Copy link
Member

The post-morgen tag is for post mortem analysis related issues like core dump problems.

Also, not sure why something not landing cleanly on an old version requires post-mortem analysis?

@gibfahn gibfahn removed the post-mortem Issues and PRs related to the post-mortem diagnostics of Node.js. label Apr 18, 2017
@refack
Copy link
Contributor

refack commented Apr 18, 2017

The post-morgen tag is for post mortem analysis related issues like core dump problems.

Sorry. it's not documented (or I couldn't find where).

Also, not sure why something not landing cleanly on an old version requires post-mortem analysis?

Since this has already landed, I could only consider this a post-mortem for it creating a regression on Windows. After my #12493 I didn't want to tag in "regression" since it's not such a big deal.

@refack
Copy link
Contributor

refack commented Apr 18, 2017

also adding ...\Git\usr\bin or any other unix tools folder, as it has some non-trivial side effects.

Out of interest, what side effects are those?

For some reason if sh.exe is in the path, make can't run properly. Also it overrides find and if you don't order your %Path% correctly, it overrides some ported tools, like curl or wget.

@refack
Copy link
Contributor

refack commented Apr 18, 2017

@mscdex
Copy link
Contributor

mscdex commented Apr 18, 2017

FWIW the contributing guide mentions that the building guide should be read when running tests and the building guide does mention in the Windows section that basic unix tools are required for some tests and that they can be installed via Git for Windows.

@refack
Copy link
Contributor

refack commented Apr 18, 2017

@mscdex aware, agree, but supporting docs with automation make for a time saver :-D

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. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

Successfully merging this pull request may close these issues.