Skip to content

Fuzz workflow failures on stable release/1.7 branch #12007

@austinvazquez

Description

@austinvazquez

The 1.7 stable branch fuzz CI workflow has started failing with the following error message:

2025/05/27 11:58:56 internal error: package "archive/tar" without types was imported from "command-line-arguments"

The error is consistent across pull requests and seems unrelated to the changes made to the branch.

@akhilerm found the errors started when this change (bump min go version to Go 1.24) was introduced to AdamKorcz/instrumentation

Through testing in a fork, I found that bumping the min version to match the version used by instrumentation repo "resolves" the issue. Therefore I have deduced the current fuzzing implementation requires the Go modules minimum versions to be compatible. The challenge I ran into was there is not clear way to pin the instrumentation repo to the prior version. I also noticed the release/1.7 branch was building fuzzers from containerd main branch. I believe both issues are related to this upstream implementation were the repositories are cloned but not pinned to a specific point in time.

I considered asking @AdamKorcz to temporarily revert the change; however, that sounds like high coupling between the upstream fuzz tooling and the fuzzed project. Instead another approach to consider is to have the container take build arguments for containerd and instrumentation repositories so each branch of containerd can build its own fuzzers and pin the instrumentation to a known good version.

Metadata

Metadata

Assignees

No one assigned

    Labels

    goPull requests that update Go code

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions