Debug ci timed out, do not merge#1805
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the playbooks/system-test-commands-options.yaml playbook to include additional flags (--show-output-of-passing-tests, --timing, and --trace) for the bats command when running the commands-options system tests. No review comments were provided, and there is no feedback to address.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
This is where it gets stuck: The test suite runs its own Docker registry using |
debarshiray
left a comment
debarshiray
left a comment
There was a problem hiding this comment.
I added --show-output-of-passing-tests --timing --trace to playbooks/system-test-runtime-environment-arch-fedora.yaml and playbooks/system-test-runtime-environment-ubuntu.yaml to see why the other jobs aren't getting stuck.
|
Maybe this is a race where the push starts before the registry container is actually ready. WDYT about introducing some way to wait on the registry? Maybe something like: local -i retries
for ((retries = 0; retries < 30; retries++)); do
if curl -fsk https://localhost:50000/v2/ > /dev/null 2>&1; then
break
fi
sleep 1
done |
|
It looks like the job is hanging on a |
Yeah probably would be a good idea. These |
|
podman-container-tools/skopeo#2878 is potentially related, with podman-container-tools/container-libs#777 being the proposed solution there |
3 participants
No description provided.