-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Conversation
@nodejs/platform-windows |
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.
LGTM
cc @nodejs/testing |
Is |
@gibfahn I don't think |
@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 |
@vsemozhetbyt Yep, that was the context I hadn't seen. I think it's fine to assume the developer will have |
@gibfahn It seems something like that is already present in the doc:
|
That's the same with other tests too. |
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.
LGTM
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.
LGTM. Happy to see stuff being removed from the common.js monolith!
Landed in 2dff3a2 |
This is causing failures for OSX testing on v6.x. did not cherry-pick. LMK if it should land |
post-mortem
bottom-lineBut 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 |
Such a test will also be a defacto documentation of what the following process is dependent on. |
Out of interest, what side effects are those?
A test that just runs through all the tools test.py expects makes sense to me, and not just for Windows. |
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? |
Sorry. it's not documented (or I couldn't find where).
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. |
For some reason if |
@gibfahn Ref: the Git4Windows installer https://github.com/git-for-windows/build-extra/blob/master/installer/install.iss#L863 |
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. |
@mscdex aware, agree, but supporting docs with automation make for a time saver :-D |
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
test
Fixes: #11469