Skip to content

Conversation

@teojgo
Copy link
Contributor

@teojgo teojgo commented May 20, 2019

  • Allow assert_reference to accept a tag parameter.

  • Use the performance tag in assert_reference at the
    check_performance stage.

Fixes #753

* Allow `assert_reference` to accept a `tag` parameter.

* Use the performance tag in `assert_reference` at the
  `check_performance` stage.
@teojgo teojgo added this to the ReFrame sprint 2019w20 milestone May 20, 2019
@teojgo teojgo requested a review from vkarak May 20, 2019 09:37
@teojgo teojgo self-assigned this May 20, 2019
- Message in case of performance failures is set by check_performance()
  including also the name of the performance variable that failed.
@vkarak vkarak changed the title [feat] Print the tag of the performance in failure message [feat] Print performance variable name in case of performance errors May 26, 2019
@codecov-io
Copy link

Codecov Report

Merging #791 into master will decrease coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #791      +/-   ##
==========================================
- Coverage   91.51%   91.51%   -0.01%     
==========================================
  Files          76       78       +2     
  Lines        9550     9791     +241     
==========================================
+ Hits         8740     8960     +220     
- Misses        810      831      +21
Impacted Files Coverage Δ
reframe/core/pipeline.py 93.28% <100%> (-0.17%) ⬇️
reframe/utility/sanity.py 98.77% <100%> (ø) ⬆️
reframe/core/modules.py 65.39% <0%> (-2.61%) ⬇️
unittests/test_policies.py 98.33% <0%> (-0.84%) ⬇️
unittests/resources/settings.py 100% <0%> (ø) ⬆️
reframe/frontend/dependency.py 93.47% <0%> (ø)
...s/resources/checks_unlisted/dependencies/normal.py 100% <0%> (ø)
reframe/frontend/cli.py 81.33% <0%> (+0.06%) ⬆️
reframe/core/exceptions.py 82.17% <0%> (+0.13%) ⬆️
... and 1 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 315b7ec...f67c8a7. Read the comment docs.

@teojgo
Copy link
Contributor Author

teojgo commented May 27, 2019

@vkarak lgtm

@vkarak
Copy link
Contributor

vkarak commented May 27, 2019

@jenkins-cscs retry dom

@vkarak vkarak merged commit e68ef06 into reframe-hpc:master May 27, 2019
@teojgo teojgo deleted the feature/message_perf_vars branch May 29, 2019 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Message about performance errors is ambiguous if multiple performance variables are present

3 participants