Skip to content

Conversation

@vkarak
Copy link
Contributor

@vkarak vkarak commented Apr 16, 2021

In order to avoid multiple warnings, this PR introduces also a caching mechanism for warnings. Warnings that are intended to be cached, must be issued with cache=True. Currently, only warnings from nomod are issued in such a way.

Fixes #1892.

…es system

In order to avoid multiple warnings, we have implemented a caching mechanism for
warnings. Warnings that are intended to be cached, must be issued with
`cache=True`.
@vkarak vkarak added this to the ReFrame sprint 21.04.1 milestone Apr 16, 2021
@vkarak vkarak requested review from jjotero and teojgo April 16, 2021 12:58
@vkarak vkarak self-assigned this Apr 16, 2021
@vkarak vkarak changed the title [feat] Issue warning if a module operation is attempted on the nomod modules system [feat] Issue a warning if a module operation is attempted on the nomod modules system Apr 16, 2021
Copy link
Contributor

@victorusu victorusu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link
Contributor

@jjotero jjotero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@vkarak vkarak merged commit 15d37da into reframe-hpc:master Apr 19, 2021
@vkarak vkarak deleted the feat/warn-when-nomod branch April 19, 2021 09:06
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.

Issue warning when a test tries to invoke a module operation on the nomod pseudo modules system

3 participants