[WIP] option for store dir relative to the target dir
Still to figure out:
- [ ] Write tests for parsing configuration.
- [ ] Write tests which set configuration and ensure that output gets written to the right spot.
- [ ] How should remapped archive directories be handled? Archive target directories are typically temporary directories which will be deleted at the end of the run. Using that as the store directory seems wrong. In that case, we may wish to use another location instead.
Codecov Report
:x: Patch coverage is 90.62500% with 12 lines in your changes missing coverage. Please review.
:white_check_mark: Project coverage is 80.20%. Comparing base (44e109c) to head (75d27f4).
Additional details and impacted files
@@ Coverage Diff @@
## main #2154 +/- ##
==========================================
+ Coverage 80.17% 80.20% +0.03%
==========================================
Files 113 114 +1
Lines 26312 26362 +50
==========================================
+ Hits 21096 21144 +48
- Misses 5216 5218 +2
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
Hi! I've been writing some tests for this in https://github.com/eduardorittner/nextest/tree/store-dir-relative. I'm not sure how to best integrate these changes? Open a PR from my branch to upstream/store-dir-relative? You just copy the commits over?
Also, regarding your third point, do you mean that when store.dir's full path is a temporary directory we should choose another directory? But how can nextest detect when it's a temporary directory? Is there a mechanism for this?
Thanks for picking this up. Let me rebase on to main and then you can submit your work as dependent on it.
But how can nextest detect when it's a temporary directory?
Only concerned about temp dirs nextest itself creates in this context, which can be tracked internally.
Rebased this on main.