Is there an existing issue for this?
Current Behavior
https://github.com/nodejs/node/pull/40319 cigtm failed cause of a quirk in the way our tests work. Because the snapshots are inside the cli repo itself, when we normally run them there is a gitHead. nodejs tests run the code in a state where there is no .git folder to find, so that attribute is missing and the tests fail.
These tests should be robust enough to handle either case, either deleting the attribute itself or hard setting it without the if statement.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- Node: 16.11.0 release candidate
- npm: 7.24.2
Is there an existing issue for this?
Current Behavior
https://github.com/nodejs/node/pull/40319cigtm failed cause of a quirk in the way our tests work. Because the snapshots are inside the cli repo itself, when we normally run them there is agitHead. nodejs tests run the code in a state where there is no.gitfolder to find, so that attribute is missing and the tests fail.These tests should be robust enough to handle either case, either deleting the attribute itself or hard setting it without the if statement.
Expected Behavior
No response
Steps To Reproduce
No response
Environment