Releases: reframe-hpc/reframe
Releases · reframe-hpc/reframe
ReFrame 2.6.1
ReFrame 2.6.1 release notes
API changes
None.
Framework
- Automatic cancellation of jobs blocked in a pending state due to reasons that require intervention of system administrators
- Support for canceling jobs
- Print detailed failure info for the sanity and performance checking algorithm
- Bugfix: Module load instructions are now emitted correctly
- Refactoring and coding style adjustments
- CI improvements
Reframe 2.6
Reframe 2.6 release notes
API changes
- New field
exclusive_accessis added that lets a check require exclusive access to compute nodes by the underlying scheduler
Framework
None
Reframe 2.5
Reframe 2.5 release notes
API changes
sourcesdirmay now beNonein which case the regression test is resourceless
Framework
- Treat properly stage and output directories if they alias each other
- Improvements of the internal launcher API to allow users to create custom launchers
- Addition of a
VisitLauncherfor the VisIt visualisation software - Support for custom execution modes
--notimestampand--timefmtoptions replaced by a single--timestamp TIMEFMToption; no timestamp directory components are appended anymore- Bug fix: crash when printing system listing and the current system was not auto-detected
- Bug fix: Environment names with slashes are now treated correctly
- Bug fix: asynchronous execution policy unit tests are now more robust
- Bug fix: job launcher options were not emitted in the job script file
Reframe 2.4
Reframe 2.4 release notes
API changes
- Support for OS variable expansion in the
variablesfield - Fixed environment loading: modules are loaded first and variables are set
afterwards - Default value of the
use_multithreadingfield is nowNone, in which case
no hint is emitted
Framework
- Brand new frontend
- Google Test look-and-feel
- Less verbose output
- Better error handling and management
- Better test statistics management
- Support for pluggable execution policies of regression tests
- New command line option
--exec-policyfor setting the execution policy of
the regression tests - Regression checks are not reused anymore across partitions and programming environments. Instead, they are cloned for every case.
- Support for asynchronous execution of regression tests
- The running phase of regression tests is executed in parallel
- Support for different maximum pending jobs per partition
- Full logging support
- Multiple logging levels
- Multiple log record handlers
- Easily configured in
reframe/settings.py - New command line option
--save-log-filesfor saving the produced log files
in the output directory of the run
- More robust user check validation
- The regression test file is first parsed for the correct definition of the
_get_checks()method and is then loaded and further validated
- The regression test file is first parsed for the correct definition of the
Reframe 2.3
Reframe 2.3 release notes
API changes
- Sanity checking returns
Trueifsanity_patternsare empty - Introduction of
readonly_filesvariable inRegressionTestAPI to allow symlinking of target files - New
propagatemember variable ofProgEnvironmentthat enables/disables the propagation of compilation flags to the underlyingmakeinvocation - Default value for programming environment flags is now
None. See Reference Guide for more information on the actual behaviour.
Framework
- More robust behaviour when no modules are loaded
- Support for virtual copying of directories
- Ability to invoke
makewithout passing it the environment's flags - Fixed sandboxing of system partitions
- Unit test and CI improvements
- Other bug fixes
Reframe 2.2
First public release.