reframe icon indicating copy to clipboard operation
reframe copied to clipboard

A powerful Python framework for writing and running portable regression tests and benchmarks for HPC systems.

Results 190 reframe issues
Sort by recently updated
recently updated
newest added

It seems that we can't specify two fixtures of the same class even with different variables. Here's a minimal reproducer: ```python import reframe as rfm from reframe.core.builtins import variable class...

Hello, Bristol site here 😀 We have a fairly large parameter space that tries to compile and run a benchmark (i.e BabelStream, with programming model and compiler as parameters). Right...

This PR adds the option of specifying custom commands to run ```reframe --detect-host-topology=topo.json``` on a remote partition to detect the topology. Previously, a clone of reframe was created in order...

prio: normal
enhancement
autodetection

More specifically, this PR adds the following enhancements: - Support for computed virtual test attributes. This mechanism allows us to extend the test queries in existing databases without having to...

prio: normal
enhancement
reporting

I sometimes get ``` WARNING: skipping test 'X': test has one or more undefined parameters ``` And recently got the same question from a user who was trying to run...

request for enhancement
prio: normal

request for enhancement
prio: normal
logging

The `--parameterize` option currently is unable to work with variables of type `typ.List[str]`. The inner `,` for the List will be treated as a `,` for the parameterize option.

request for enhancement
prio: normal

Currently, only the following import vectors are supported: - From perflogs - From other DB files ### Todos - [ ] Import from JSON reports (4.7 and pre 4.7) -...

prio: normal
enhancement
reporting

In a test with multiple performance variables (figures of merit), if one of them fails in performance, the whole tests is marked (correctly) as a failure. However, when logging the...

request for enhancement
prio: normal

We shoud try to cleanup and update the base containers + the Dockerfiles used for the tutorial and unittests.

prio: normal
automation
packaging