Skip to content

Tests: the host probe test runs the machine's own podman and times out #216

Closed

Description

@harenome

Priority

low. The defect is in test code only. It fails the backend suite in a change that does not touch hosts.

Components

  • app/nullius (backend)
  • app/web (routes)
  • templates and static files
  • docs and the site
  • catalogue (benchmarks, agents, capabilities)
  • the standard (ports, kits, relay, runs)
  • CI, workflows and skills

Tests only: app/tests/test_hosts.py.

Evidence

On #215, whose diff does not touch hosts.py or test_hosts.py, the backend suite failed once in CI (job, attempt 1). A rerun passed.

ERROR: test_the_probe_says_when_the_host_s_docker_has_userns_remap (tests.test_hosts.ConnectionTest...) (options='[name=seccomp,profile=builtin name=userns name=cgroupns]')
  File ".../app/tests/test_hosts.py", line 105, in test_the_probe_says_when_the_host_s_docker_has_userns_remap
  File ".../app/nullius/hosts.py", line 213, in test
  File ".../app/tests/test_hosts.py", line 103, in <lambda>
subprocess.TimeoutExpired: Command '['sh', '-c', 'printf \'ok\\n\'; for c in uv docker podman harbor; ...']' timed out after 12.0 seconds

The test runs hosts.PROBE in a local shell, with a stub docker first on PATH. The rest of PATH is /usr/bin:/bin, so the probe also finds the machine's own programs. For each of docker and podman it finds, it runs $c ps. A machine with a real podman in /usr/bin therefore runs podman ps inside the test, and the test waits for it under the probe's 12 s timeout.

The CI runner has one: the job ran on GitHub's Ubuntu 26.04 image 20261116.202, whose software list includes Podman 5.7.0. Why podman ps took that long on the runner was not checked. A first rootless call may set up its storage.

A podman in /usr/bin that takes 20 s reproduces the failure. Without it, the test passes in 6 ms.

Screenshot

No response

Reproduction

  1. In a python:3.12 container, on main, write /usr/bin/podman as #!/bin/sh and sleep 20, and make it executable.
  2. From app/, run python3 -m unittest tests.test_hosts.ConnectionTest.test_the_probe_says_when_the_host_s_docker_has_userns_remap.
  3. The test fails with subprocess.TimeoutExpired: ... timed out after 12.0 seconds. Remove the file and it passes.

Expected

The test depends only on its own stub programs. A program installed on the machine running the suite does not run during the test or change its result.

Acceptance

  • The test's PATH holds only its stub docker and the few programs the test and the probe need (sh, sed, grep, hostname), not /usr/bin or /bin.
  • A docker, podman, uv or harbor installed on the machine does not run during the test.
  • The test still checks both answers, docker_userns true and false.
  • The test passes with a slow podman in /usr/bin.

Dependencies and related

Activity

  1. added theissue type on Nov 18, 2026
  2. added
    bugSomething isn't working
    P3When convenient: wording, layout, tests
    on Nov 18, 2026
  3. added a commit that references this issue on Nov 19, 2026
    f094cba
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3When convenient: wording, layout, testsbugSomething isn't working

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions