#3576·youki

Add update command integration tests to contest

Author: saku3Created Jun 1, 2026Updated Sep 6, 2026

Description

Add update integration tests to tests/contest equivalent to tests/integration/update.bats in runc, then make youki pass them.

Motivation

The contest framework (Rust-based OCI runtime integration tests) currently has no coverage for update functionality. The existing BATS-based tests in runc's update.bats cover this area but are not available through contest.

Implement contest tests

Add the following tests to tests/contest.

These tests are skipped when running with youki, as the required functionality is not fully implemented yet.

  • update cgroup v1/v2 common limits (#3580)
  • update cgroup cpu limits
  • update pids.limit (#3595 )
  • cpu burst (#3592)
  • set cpu period with no quota (#3592)
  • set cpu period with no quota (invalid period) (#3592)
  • set cpu quota with no period (#3592)
  • update cpu period with no previous period/quota set (#3614)
  • update cpu quota with no previous period/quota set (#3614)
  • update cpu period in a pod cgroup with pod limit set (#3614)
  • update cgroup cpu.idle (#3614)
  • update cgroup cpu.idle via systemd v252+ (#3614)
  • update cgroup v2 resources via unified map
  • update cpuset parameters via resources.CPU
  • update cpuset parameters via v2 unified map
  • update cpuset cpus range via v2 unified map
  • update rt period and runtime
  • update devices [minimal transition rules]
  • update paused container
  • update memory vs CheckBeforeUpdate
  • update per-device iops/bps values