Skip to content

Fix breaking api tests on windows #4001

Open

Description

@natasha41575

Some tests in the api module break on windows, so we skip them for now.

See the comment here: https://github.com/kubernetes-sigs/kustomize/blob/324581594c9cf92d8604366477ba83868cdf921b/.github/workflows/go.yml

Activity

  1. added
    triage/acceptedIndicates an issue or PR is ready to be actively worked on.
    area/apiissues for api module
    on Jun 16, 2021
  2. added
    needs-kindIndicates a PR lacks a `kind/foo` label and requires one.
    on Jun 16, 2021
  3. added
    kind/test-coverageCategorizes issue or PR as related to a gap in or problem with our test coverage.
    on Jun 16, 2021
  4. removed
    needs-kindIndicates a PR lacks a `kind/foo` label and requires one.
    on Jun 16, 2021
  5. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Jul 2, 2021
  6. k8s-triage-robot commented on Sep 30, 2021

    @k8s-triage-robot

    The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

    This bot triages issues and PRs according to the following rules:

    • After 90d of inactivity, lifecycle/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

    You can:

    • Mark this issue or PR as fresh with /remove-lifecycle stale
    • Mark this issue or PR as rotten with /lifecycle rotten
    • Close this issue or PR with /close
    • Offer to help out with Issue Triage

    Please send feedback to sig-contributor-experience at kubernetes/community.

    /lifecycle stale

  7. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Sep 30, 2021
  8. k8s-triage-robot commented on Oct 30, 2021

    @k8s-triage-robot

    The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

    This bot triages issues and PRs according to the following rules:

    • After 90d of inactivity, lifecycle/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

    You can:

    • Mark this issue or PR as fresh with /remove-lifecycle rotten
    • Close this issue or PR with /close
    • Offer to help out with Issue Triage

    Please send feedback to sig-contributor-experience at kubernetes/community.

    /lifecycle rotten

  9. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Oct 30, 2021
  10. natasha41575 commented on Nov 3, 2021

    @natasha41575
    ContributorAuthor

    /remove-lifecycle rotten

  11. removed
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    on Nov 3, 2021
  12. k8s-triage-robot commented on Feb 1, 2022

    @k8s-triage-robot

    The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

    This bot triages issues and PRs according to the following rules:

    • After 90d of inactivity, lifecycle/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

    You can:

    • Mark this issue or PR as fresh with /remove-lifecycle stale
    • Mark this issue or PR as rotten with /lifecycle rotten
    • Close this issue or PR with /close
    • Offer to help out with Issue Triage

    Please send feedback to sig-contributor-experience at kubernetes/community.

    /lifecycle stale

  13. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Feb 1, 2022
  14. 57 remaining items

  15. ammachado commented on Sep 24, 2026

    @ammachado

    /assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/apiissues for api modulehelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/test-coverageCategorizes issue or PR as related to a gap in or problem with our test coverage.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions