Beth Griggs

Curious if we should consider moving this to `nodejs/node` (and potentially tagging with `good first issue`?). The automation would be on that repository, and this issue would probably get more...

I spent a while yesterday trying to remove the colour codes from the output. I thought adding `"envVar": { "TAP_COLORS": 0 }` in the lookup would be enough ([commit](https://github.com/BethGriggs/citgm/commit/6e893ea89a8d0ac0881b820b8126a726b812ca69#diff-c74147f2051890f8e116e39ec74462ecbfb4a000ff8eecd5a9a2316fdfd859beR366)). But,...

> This could be a cool solution: https://plugins.jenkins.io/ansicolor/ Thoughts @nodejs/citgm @nodejs/build? I know adding any more plugins is 'yet another thing to update'. But, the last release was 8 months...

Stripping the codes, one of the errors: ``` error: | ​ FAIL ​ test/lib/commands/config.js error: | ✖ output matches snapshot error: | error: | test/lib/commands/config.js error: | 105 | await...

I'm guessing this could be more a CITGM side-effect - it's likely we're setting different `tmp` directories in CITGM runs and the test suite assumes a more specific location. I...

FYI @ljharb - it seems there are other issues in addition to the windows issue surfaced in #894

Seems plausible. We do have both ubuntu1804 and ubuntu1604 in the matrix on Jenkins and [it's failing in the same way there too](https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker-nobuild/1150/nodes=ubuntu1804-64/console). But, that's possibly a difference in our...

Sure, or maybe you could rename https://github.com/nodejs/build/issues/2913 to be a generic request and request an additional os/arch within there? I don't personally see the need to gather approvals for your...

@ljharb I got a little creative with our Jenkins job and managed to get the output of that command in the output - see https://ci.nodejs.org/job/citgm-smoker-nobuild/nodes=ubuntu1804-64/1159/consoleText

That seems to have worked 🎉 - https://ci.nodejs.org/job/citgm-smoker-nobuild/nodes=ubuntu1804-64/1163/console