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.

Sign up for GitHub

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

Jump to bottom

Clean-up techdebt around uses of side effect counters in kernel tests #5179

Open
Tracked by #5011
alexghr opened this issue Mar 13, 2024 · 0 comments
Open
Tracked by #5011

Clean-up techdebt around uses of side effect counters in kernel tests #5179

alexghr opened this issue Mar 13, 2024 · 0 comments

Comments

@alexghr
Copy link
Contributor

alexghr commented Mar 13, 2024

It's unclear right now how start/end side effect counters are set in unit tests of the kernels. We should refactor the code to make it explicit what counters mocked functions are expected to run between.

See #5129 (comment)
@github-project-automation github-project-automation bot moved this to Todo in A3 Mar 13, 2024
@alexghr alexghr mentioned this issue Mar 13, 2024
Merged
@just-mitch just-mitch added this to the ITN - Node Security milestone Mar 13, 2024
@just-mitch just-mitch mentioned this issue Mar 13, 2024
Open
@iAmMichaelConnor iAmMichaelConnor removed this from the ITN - Node Security milestone Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
A3
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
3 participants
@alexghr @iAmMichaelConnor @just-mitch