ember-cli causing CITGM to hard fail on Windows
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 606
- Forks
- 157
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 3
Description
- 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:
15:49:13 error: failure | Test Timed Out
15:49:17 [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\ADMINI~1\AppData\Local\Temp\dbc0cb80-9c24-40ad-95d1-509c6b6462a7\ember-cli'] {
15:49:17 errno: -4082,
15:49:17 code: 'EBUSY',
15:49:17 syscall: 'rmdir',
15:49:17 path: 'C:\\Users\\ADMINI~1\\AppData\\Local\\Temp\\dbc0cb80-9c24-40ad-95d1-509c6b6462a7\\ember-cli'
15:49:17 }
https://ci.nodejs.org/job/citgm-smoker/nodes=win-vs2017/2348/console
I've seen this on v13.x and v14.x. The hard fail means that Windows results do not appear in the aggregated results view, so we're potentially missing some failures.
Contributor guide
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 reproducing the ember-cli failure in the CITGM smoker job on Windows, using the linked citgm-smoker console output as the initial reference. Trace the cleanup path that reports EBUSY while removing the temporary ember-cli directory; done means the Windows run no longer hard-fails and its results appear in the aggregated view.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100