fix(tests/gradle): explicitly use build output directory
Metadata
Current evaluation
Merged a fix for Gradle tests using the build output directory instead of user.dir to prevent daemon resets from breaking test writes. Resolves #1304. Approved by two reviewers and passed all CI checks.
Suggested action: —
No scores available.
Issue body
Instead of user.dir which may be reset by the Gradle daemon use gradle build output directory to write the test file
Fixes #1304
- [x] Have you followed the guidelines for contributing?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you successfully run `make lint && make test`?
- [ ] Have you added an entry to the changelog (`docs/reference/changelog.rst`)?
---
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged a fix for Gradle tests using the build output directory instead of user.dir to prevent daemon resets from breaking test writes. Resolves #1304. Approved by two reviewers and passed all CI checks. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a fix for Gradle tests that explicitly uses the build output directory instead of user.dir, preventing failures when the Gradle daemon resets the working directory. Resolves #1304. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #758 fix(testing): don't change the output artifact location | craft-application | merged | Merged fix for #752 that keeps test output artifacts in the standard location instead of moving them to a spread subdirectory. Approved by reviewers and passed CI checks prior to merge. |