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

Always use cgroups in runguard. #2339

Merged
merged 1 commit into from
Feb 22, 2024
Merged

Always use cgroups in runguard. #2339

merged 1 commit into from
Feb 22, 2024

Conversation

meisterT
Copy link
Member

There is no benefit in not using them, the library needs to be installed anyway to be able to compile runguard and it makes the flow in runguard more consistent.

Work towards #luigi (https://docs.google.com/document/d/1WZRwdvJUamsczYC7CpP3ZIBU8xG6wNqYqrNJf7osxYs/edit).

There is no benefit in not using them, the library needs to be installed
anyway to be able to compile runguard and it makes the flow in runguard
more consistent.
Copy link
Member

@eldering eldering left a comment

Choose a reason for hiding this comment

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

Makes sense: this is from the time we were switching from resource limits to cgroups.

@meisterT meisterT added this pull request to the merge queue Feb 22, 2024
Merged via the queue into DOMjudge:main with commit 89fe096 Feb 22, 2024
22 checks passed
@meisterT meisterT deleted the cgroup branch February 22, 2024 21:26
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.

3 participants