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

cpu burst test failures on Ubuntu 24.04 #4373

Closed
kolyshkin opened this issue Aug 13, 2024 · 2 comments · Fixed by #4374
Closed

cpu burst test failures on Ubuntu 24.04 #4373

kolyshkin opened this issue Aug 13, 2024 · 2 comments · Fixed by #4374

Comments

@kolyshkin
Copy link
Contributor

Description

Observed in #4370, #4360. Was not happening 3 days ago.

not ok 251 cpu burst
# (from function `check_cgroup_value' in file tests/integration/helpers.bash, line 270,
#  from function `check_cpu_burst' in file tests/integration/helpers.bash, line 320,
#  in test file tests/integration/update.bats, line 343)
#   `check_cpu_burst 500000' failed
# runc spec --rootless (status=0):
#
# runc run -d --console-socket /tmp/bats-run-E7MhUu/runc.72ZYse/tty/sock test_update (status=0):
#
# current 0 !? 0
# runc update test_update --cpu-period 900000 --cpu-burst 500000 (status=0):
#
# current 500000 !? 500

Suddenly it fails for me locally, too:

 ✗ cpu burst
   (from function `check_cgroup_value' in file tests/integration/helpers.bash, line 270,
    from function `check_cpu_burst' in file tests/integration/helpers.bash, line 320,
    in test file tests/integration/update.bats, line 343)
     `check_cpu_burst 500000' failed
   runc spec (status=0):
   
   runc run -d --console-socket /tmp/bats-run-7HL8bU/runc.7u79IU/tty/sock test_update (status=0):
   
   current 0 !? 0
   runc update test_update --cpu-period 900000 --cpu-burst 500000 (status=0):
   
   current 500000 !? 500

Steps to reproduce the issue

Describe the results you received and expected

no failures

What version of runc are you using?

[kir@kir-tp1 runc]$ ./runc --version
runc version 1.2.0-rc.2+dev
commit: v1.2.0-rc.2-31-g6602681d
spec: 1.2.0
go: go1.22.5
libseccomp: 2.5.5

Host OS information

No response

Host kernel information

No response

@kolyshkin
Copy link
Contributor Author

Relevant commits/PRs:

@kolyshkin
Copy link
Contributor Author

This is probably caused by this kernel commit: https://lore.kernel.org/all/[email protected]/

I.e. the new behavior is right, the old one is wrong. To account for older kernels we have to check both values.

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 a pull request may close this issue.

1 participant