citgm icon indicating copy to clipboard operation
citgm copied to clipboard

Canary in the Gold Mine

Results 111 citgm issues
Sort by recently updated
recently updated
newest added

- **Node Version**: Multiple - **CitGM Version**: Latest - **Platform**: Windows It looks like ember-cli is causing CITGM to hard fail on Windows with the following error: ```bash 15:49:13 error:...

https://ci.nodejs.org/job/citgm-smoker/2082/nodes=ubuntu1804-64/testReport/junit/(root)/citgm/zeromq_v6_0_0_beta_2/ I don't know if it's something that we can reasonably install on all CI hosts. Until then, we should probably skip the module.

Refs: https://github.com/nodejs/node/pull/31818#issuecomment-619133779

The tap testing framework has improved a lot since we initially started this project. One new(er) addition is [official APIs for fixtures](https://node-tap.org/docs/api/fixtures/). I'm not 100% exactly which tests need to...

good first issue

CI run: https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/1688/ I expect it to fail on Windows because of https://github.com/nodejs/citgm/issues/652 but if other platforms are red, we should look into the failures.

It seems like yarn uses `fs.futimes()` during install and that does not work on AIX versions before 7.1. What about skipping AIX by default if yarn is used?

I created a project to track them: https://github.com/nodejs/citgm/projects/2 The reason is mainly the deprecation of the Buffer constructor. Note: currently, npm itself fails to run with `--throw-deprecation` (https://github.com/nodejs/node/issues/23013). You can...

meta

* **Node Version**: 8.9.0 (maybe all) * **CitGM Version**: 2.0.14 * **Platform**: all Previously passing on 1.10.3 ```bash ▶ citgm sodium-native ~/wrk/com/DANGER/node 7s (v8.9.1-proposal) info: starting | sodium-native info: lookup...

@MylesBorins and myself have often discussed how we would like to re-design the citgm logger. I will create this issue here and then let people make any suggestions as to...

enhancement

Perhaps this should be extra verbose when setting a specific test path

good first issue