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

BUG: syscalls_file fixes #111

Closed

Conversation

rgbriggs
Copy link
Contributor

A couple of fixes for the syscalls_file test:

  • Rename the user message label for consistency "syncmarker"
  • Restrict the open* syscall monitoring to the test directory to avoid oom failures

All other tests use "syncmarker".  Reword user message for consistency.

Signed-off-by: Richard Guy Briggs <[email protected]>
… failure

Due to the overly broad logging of open{,at,at2} syscalls, some test systems
have been overwhelmed by systemd-journald activity triggering oom, causing the
test to fail.

Restrict the test rules to the expected test directory.

Signed-off-by: Richard Guy Briggs <[email protected]>
@rgbriggs rgbriggs force-pushed the ghat-syscalls_file-syncmarker branch from de552ca to 9bdbc65 Compare September 29, 2023 13:21
@pcmoore pcmoore changed the title Ghat syscalls file syncmarker BUG: syscalls_file fixes Aug 28, 2024
@pcmoore
Copy link
Contributor

pcmoore commented Aug 28, 2024

Merged via 22feeba, thanks @rgbriggs!

@pcmoore pcmoore closed this Aug 28, 2024
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.

2 participants