Skip to content

Conversation

@vkarak
Copy link
Contributor

@vkarak vkarak commented Sep 17, 2025

Closes #3551.

@vkarak vkarak added this to the ReFrame 4.8.4 milestone Sep 17, 2025
@vkarak vkarak requested review from ekouts and teojgo September 17, 2025 16:31
@vkarak vkarak self-assigned this Sep 17, 2025
@vkarak vkarak added the bugfix label Sep 17, 2025
@codecov
Copy link

codecov bot commented Sep 17, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.22%. Comparing base (ff41341) to head (a332dec).
⚠️ Report is 759 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3553      +/-   ##
==========================================
+ Coverage   86.66%   91.22%   +4.55%     
==========================================
  Files          61       62       +1     
  Lines       12140    13465    +1325     
==========================================
+ Hits        10521    12283    +1762     
+ Misses       1619     1182     -437     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@vkarak vkarak changed the base branch from develop to master September 17, 2025 16:38
Copy link
Contributor

@ekouts ekouts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me it's not clear what * should * happen with the old output directory. People may be confused by looking at the output of old runs when they are testing --dry-run. On the other hand I understand that removing the old results with a "dry run" option can also be unwanted behaviour, so lgtm!

@github-project-automation github-project-automation bot moved this from Todo to In Progress in ReFrame Backlog Sep 18, 2025
@vkarak
Copy link
Contributor Author

vkarak commented Sep 18, 2025

For me it's not clear what * should * happen with the old output directory. People may be confused by looking at the output of old runs when they are testing --dry-run. On the other hand I understand that removing the old results with a "dry run" option can also be unwanted behaviour, so lgtm!

Removing the output directory is a totally undesired side effect, as this is supposed to hold scripts and data from what it has been actually executed. In the docs we state that --dry-run generates the scripts in the stage directory and, also, in dry-run mode we do not copy back to the output directory anything from the test, because what is in keep_files is likely not produced. So, essentially, the --dry-run mode was literally just wiping out the output directory.

@vkarak vkarak merged commit e1a3bc5 into reframe-hpc:master Sep 18, 2025
39 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in ReFrame Backlog Sep 18, 2025
@vkarak vkarak deleted the bugfix/dry-run-outputdir branch September 18, 2025 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

--dry-run wipes out the output test directory

2 participants