Skip to content

Commit

Permalink
add a test case for runc update cpu burst
Browse files Browse the repository at this point in the history
In issue #4210, if we don't provide `--cpu-burst` in `runc update`,
the value of cpu burst will always set to 0.

Signed-off-by: lifubang <lifubang@acmcoder.com>
  • Loading branch information
lifubang committed Apr 3, 2024
1 parent 0680e2b commit afcb9c2
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions tests/integration/update.bats
Original file line number Diff line number Diff line change
Expand Up @@ -344,6 +344,14 @@ EOF
[ "$status" -eq 0 ]
check_cpu_burst 500000

# issue: https://github.com/opencontainers/runc/issues/4210
# for systemd, cpu-burst value will be cleared, it's a known issue.
if [ ! -v RUNC_USE_SYSTEMD ]; then
runc update test_update --memory 100M
[ "$status" -eq 0 ]
check_cpu_burst 500000
fi

runc update test_update --cpu-period 900000 --cpu-burst 0
[ "$status" -eq 0 ]
check_cpu_burst 0
Expand Down

0 comments on commit afcb9c2

Please sign in to comment.