ReFrame ignores num_cpus_per_task for CompileOnlyRegressionTest
See original GitHub issueI tried setting num_cpus_per_task = 4
in the class body of a CompileOnlyRegressionTest
, but ReFrame ignores it.
I also tried setting it with:
@run_after('setup')
def set_cpus_per_task(self):
self.job.num_cpus_per_task = 4
but apparently there is no job
object defined for CompileOnlyRegressionTest
, as I get this error:
AttributeError: 'NoneType' object has no attribute 'num_cpus_per_task'
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Tutorial 2: Customizing Further a Regression Test - ReFrame
In this tutorial we will present common patterns that can come up when writing regression tests with ReFrame. All examples use the configuration...
Read more >reframe/pipeline.py at master - GitHub
from reframe.core.meta import RegressionTestMeta ... :attr:`executable_opts` attributes are ignored. ... Number of CPUs per task required by this test.
Read more >ReFrame Documentation - Read the Docs
ReFrame is a powerful framework for writing system regression tests and benchmarks, specifically targeted to HPC systems.
Read more >A regression framework for checking the health of large HPC ...
Abstract—In this paper, we present a new framework for writing regression tests for HPC systems, called REFRAME. The goal of this framework is...
Read more >Introducing Slurm - Princeton Research Computing
The mathematical product of nodes, ntasks and cpus-per-task is equal to the total number of CPU-cores that you are requesting in your Slurm...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
self.num_cpus_per_task
did not work, butself.build_job.num_cpus_per_task
does work (that’s probably what you meant?)as a suggestion, maybe you could automatically set
self.build_job.num_cpus_per_task
equal toself.num_cpus_per_task
if not defined?anyway, thanks a lot for the help!
Opened #2315.