microsoft / microsoft/DefinitelyTyped-tools
test-all sometimes tests packages more than once
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 423
- Forks
- 237
- Avg merge
- 18h 18m
- Merged PRs (30d)
- 11
Description
When running npm run test-all in the DT repo I sometimes see packages being tested twice. Oftentimes locally when making changes to React but now I also caught one in CI. Notice how it starts cavy, cavy fails and then it starts cavy again:
Originally reported in https://discord.com/channels/508357248330760243/757992230077333655/1089617477274718208
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running npm run test-all in the DefinitelyTyped-tools repository and compare the output when a package such as cavy is tested. Then inspect the linked CI job, especially the test step, to determine why a package can be scheduled twice. Done means each package is tested once per run, including when a test fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, testing-qa, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100