reframe
reframe copied to clipboard
A powerful Python framework for writing and running portable regression tests and benchmarks for HPC systems.
The main elements introduced by this PR are: 1. The `@xfail` decorator to mark a test as an expected sanity failure. 2. The `xfail()` builtin to mark reference tuples as...
Currently, the delimiter is always the comma, which can be problematic depending on which columns we want to show.
When used for test filtering `-n` removes the whitespace before the parameters, but this is not the case when it's used for result filtering with the `--{list/describe}-stored-testcases` options.
I think build jobs are not killed on abort https://github.com/reframe-hpc/reframe/blob/73441fac5598484300c807ce5357e6ff0d24b395/reframe/frontend/executors/__init__.py#L514-L524
The way we handle this currently is very monolithic. A test can only have a single `sourcesdir` which will be copied over to its stage directory. Also there is the...
ReFrame historically has tried to avoid over-specification of the node request, so it officially supported only `num_tasks` and `num_tasks_per_node` as test attributes. This however can be problematic with some scheduler...
This is wrong, as the test's `time_limit` should override any time limit set at the partition level. The workaround is to pass `-S [test.]time_limit=` to set it explicitly.
When using the ReFrame configuration setting: ```shell sched_options: use_nodes_option: True ``` it would be useful to have ReFrame log the number of allocated nodes. At the moment there is a...
The `--flex-alloc-nodes=NODESTATE` does not support multiple states with no intersecting names under slurm. I am trying to submit some daily flexible single core jobs with `--flex-alloc-nodes=idle*` , but it would...
Now we have plenty of places where commands from either the configuration or the test are emitted and we need special [tricks]() to generate multiple steps. It would be better...