Skip to content

Tests should not use Setenv as it prevents parallelization #3081

@apostasie

Description

@apostasie

Description

Tests using Setenv cannot be parallelized safely.

Instead, we should modify Env for whichever Cmd needs it without touching the global environment.

Steps to reproduce the issue

n.a.

Describe the results you received and expected

n.a.

What version of nerdctl are you using?

1.7.6

Are you using a variant of nerdctl? (e.g., Rancher Desktop)

None

Host information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/cie.g., CI failurebugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions