Skip to content

build: Style fix#1802

Merged
debarshiray merged 3 commits into
containers:mainfrom
debarshiray:wip/rishi/src-go-build-wrapper-extldflags-use-comma-not-equal
Jun 8, 2026
Merged

build: Style fix#1802
debarshiray merged 3 commits into
containers:mainfrom
debarshiray:wip/rishi/src-go-build-wrapper-extldflags-use-comma-not-equal

Conversation

@debarshiray

Copy link
Copy Markdown
Member

Use a comma to pass an argument to an external linker option instead of an equal sign for consistency. It was originally copied verbatim from the NVIDIA Container Toolkit [1], which itself has this inconsistency.

Fallout from 66280a6

[1] NVIDIA Container Toolkit commit 772cf77dcc2347ce
NVIDIA/nvidia-container-toolkit@772cf77dcc2347ce
NVIDIA/nvidia-container-toolkit#333

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the go-build-wrapper script to correct the syntax for passing the --unresolved-symbols option to the linker via -Wl, changing the separator from = to ,. There are no review comments, and I have no feedback to provide.

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.

debarshiray added a commit to debarshiray/toolbox that referenced this pull request Jun 5, 2026
Use a comma to pass an argument to an external linker option instead of
an equal sign for consistency.  It was originally copied verbatim from
the NVIDIA Container Toolkit [1], which itself has this inconsistency.

Fallout from 66280a6

[1] NVIDIA Container Toolkit commit 772cf77dcc2347ce
    NVIDIA/nvidia-container-toolkit@772cf77dcc2347ce
    NVIDIA/nvidia-container-toolkit#333

containers#1802
@debarshiray debarshiray force-pushed the wip/rishi/src-go-build-wrapper-extldflags-use-comma-not-equal branch from def89d8 to 730326c Compare June 5, 2026 18:30
@debarshiray debarshiray requested a review from Jmennius as a code owner June 5, 2026 18:30
Use a comma to pass an argument to an external linker flag instead of an
equal sign for consistency.  It was originally copied verbatim from the
NVIDIA Container Toolkit [1], which itself has this inconsistency.

Fallout from 66280a6

[1] NVIDIA Container Toolkit commit 772cf77dcc2347ce
    NVIDIA/nvidia-container-toolkit@772cf77dcc2347ce
    NVIDIA/nvidia-container-toolkit#333

containers#1802
@debarshiray debarshiray force-pushed the wip/rishi/src-go-build-wrapper-extldflags-use-comma-not-equal branch from 730326c to ebee6ab Compare June 5, 2026 18:38
@debarshiray

Copy link
Copy Markdown
Member Author

recheck

@debarshiray

Copy link
Copy Markdown
Member Author

Build failed. https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/local/buildset/87df61a31a05441ba3227d6ba203ab6f

system-test-fedora-rawhide-commands-options TIMED_OUT in 2h 00m 34s
system-test-fedora-44-commands-options TIMED_OUT in 1h 45m 29s

It's the same failure that we have been seeing lately:

fedora-rawhide | 1..239
fedora-rawhide | # test suite: Set up
RUN END RESULT_TIMED_OUT: [untrusted : github.com/containers/toolbox/playbooks/system-test-commands-options.yaml@main]
POST-RUN START: [trusted : softwarefactory-project.io/config/playbooks/base/post.yaml@master]

It looks like it's stuck downloading and caching the OCI images used by the test suite during the set-up stage.

Everything was fine on the 28th of May. The system-test-fedora-rawhide-commands-options job started consistently timing out and some others started to get some intermittent node failures on the 30th of May. The system-test-fedora-44-commands-options job started timing out on the 4th of June and the intermittent node failures continued.

Initially, I thought that it was some passing problem with the infrastructure or Fedora Rawhide, and then the Fedora 44 failures started.

@TristanCacqueray any idea off the top of your head what could be wrong? Otherwise, I will dig deeper into it by enabling some extra debug.

@debarshiray debarshiray merged commit 5ee1572 into containers:main Jun 8, 2026
9 of 10 checks passed
@debarshiray debarshiray deleted the wip/rishi/src-go-build-wrapper-extldflags-use-comma-not-equal branch June 8, 2026 21:38
@TristanCacqueray

Copy link
Copy Markdown
Contributor

@debarshiray in success build, it takes 44 second for the bats command to display the first result, so it's not clear what's going on. As a first step, we can add some debug flags to see what's happening when the TIMED_OUT occur, e.g. from the job-output.txt:

2026-06-09 03:14:31.181524 | TASK [Run the commands-options system tests]
2026-06-09 03:14:38.250064 | fedora-43 | 1..239
2026-06-09 03:14:38.281687 | fedora-43 | # test suite: Set up
2026-06-09 03:15:22.774737 | fedora-43 | ok 1 version: Check version using option --version

… timed out:

2026-06-08 10:44:21.953627 | TASK [Run the commands-options system tests]
2026-06-08 10:44:29.840753 | fedora-44 | 1..239
2026-06-08 10:44:29.870321 | fedora-44 | # test suite: Set up
2026-06-08 12:27:29.922238 | RUN END RESULT_TIMED_OUT: [untrusted : github.com/containers/toolbox/playbooks/system-test-commands-options.yaml@main]

Let's see if #1805 will shed some light.

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 this pull request may close these issues.

3 participants