Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bugfix] Fix behaviour of set_var_default() when setting a variable after test initialisation #3050

Merged
merged 1 commit into from
Nov 22, 2023

Conversation

vkarak
Copy link
Contributor

@vkarak vkarak commented Nov 21, 2023

Closes #3049.

Copy link

codecov bot commented Nov 21, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (6e60957) 86.70% compared to head (f6d5470) 86.70%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3050   +/-   ##
=======================================
  Coverage   86.70%   86.70%           
=======================================
  Files          61       61           
  Lines       12002    12002           
=======================================
  Hits        10406    10406           
  Misses       1596     1596           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@vkarak vkarak merged commit 21d1806 into reframe-hpc:master Nov 22, 2023
18 checks passed
@vkarak vkarak deleted the bugfix/set-var-default branch November 22, 2023 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

set_var_default() still sets the variable even if it's set just before it
2 participants