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

Emit warning if memory.peak cannot be be captured with cgroup v2. #2775

Merged
merged 1 commit into from
Nov 3, 2024

Conversation

meisterT
Copy link
Member

@meisterT meisterT commented Nov 2, 2024

Note that this is only about memory high watermark reporting, not about whether the submission is killed.

Fixes #2763.

Copy link
Contributor

@Kevinjil Kevinjil left a comment

Choose a reason for hiding this comment

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

With the change suggested by CI, LGTM.

Note that this is only about memory high watermark reporting, not about
whether the submission is killed.

Fixes DOMjudge#2763.
@meisterT meisterT added this pull request to the merge queue Nov 3, 2024
Merged via the queue into DOMjudge:main with commit 8f8f4c0 Nov 3, 2024
28 checks passed
@meisterT meisterT deleted the oldkernelv2 branch November 3, 2024 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Memory usage does not get reported
3 participants