rm_rf fails for a set of tests
See original GitHub issuei started to observe the following on the features branch:
pytest.PytestWarning: (rm_rf) error removing /tmp/pytest-of-rpfannsc/garbage-3bad3bc3-af58-4b47-8b7e-ea772115f6ea/test_cache_failure_warns0/.pytest_cache: [Errno 13] Permission denied: '.pytest_cache'
together with the pytest warning configuration this means the “world” breaks very regular
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (14 by maintainers)
Top Results From Across the Web
Failed rmRF: EPERM: operation not permitted, unlink 'XXXXXX'
Hi, we got this problem during a release deployment. ... If it is set as false, then our system will not execute rmrf...
Read more >Copy Files using Clean Target Folder sometimes fails ... - GitHub
I have release definitions having the "Copy Files" task and "Clean target folder" option checked. Most of the deployments are successfull, ...
Read more >Business 35905 John H. Cochrane Problem Set 6 We're going ...
Subtract the risk free rate rf from the 25 test assets to make them ... Nonetheless, I won't make you do the GMM...
Read more >Why does Azure task ExtractFiles sometimes fail?
I have a yaml release pipeline that uses the 'ExtractFiles@1' task setup like this: - task: ExtractFiles@1 inputs: archiveFilePatterns: ...
Read more >Test Assets and Weak Factors - UConn Finance Department
correlated exposures to a given set of test assets. ... the extent that it allows for weak factors that the standard PCA fails...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@nicoddemus we should ensure this particular warning never turns into a error
Cool, https://github.com/pytest-dev/pytest/pull/6136.
The warning only happens when pytest cleans them up, which only happens later (it keeps the most recent ones).