Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Flake - test TestExamples/v1alpha1/taskruns/step-script #4433

Closed
pritidesai opened this issue Dec 15, 2021 · 5 comments
Closed

Flake - test TestExamples/v1alpha1/taskruns/step-script #4433

pritidesai opened this issue Dec 15, 2021 · 5 comments
Labels
kind/flake Categorizes issue or PR as related to a flakey test lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@pritidesai
Copy link
Member

As part of the PR #4429, alpha integration tests ran into a failure:

test TestExamples/v1alpha1/taskruns/step-script 10m3s
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=test\sTestExamples\/v1alpha1\/taskruns\/step\-script$'
    init_test.go:135: Create namespace arendelle-xwdmb to deploy to
    init_test.go:163: Verify SA "default" is created in namespace "arendelle-xwdmb"
    examples_test.go:62: Failed waiting for task run done: timed out waiting for the condition

The detailed logs can be found here.

/kind flake
@tekton-robot tekton-robot added the kind/flake Categorizes issue or PR as related to a flakey test label Dec 15, 2021
@jerop jerop added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Feb 7, 2022
@lbernick lbernick moved this to Todo in Pipelines V1 Feb 7, 2022
@lbernick lbernick moved this from Todo to In Progress in Pipelines V1 Feb 7, 2022
@lbernick lbernick moved this from In Progress to Todo in Pipelines V1 Feb 7, 2022
@dibyom dibyom added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Apr 25, 2022
@abayer
Copy link
Contributor

abayer commented Jun 22, 2022

This specific flake should be dealt with by #5005, since that removes the v1alpha1 tests entirely, but I believe this (and other v1alpha1 flakes, namely #4645, #4427, and #4415) may well continue to be flaky in their v1beta1 equivalents. In general, I think most, if not all, of the flakes we hit in e2e tests are due to timing issues on clusters created in our test project in GKE, since I've failed to reproduce any of them in repeated runs in a local kind setup...

@tekton-robot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 20, 2022
@tekton-robot
Copy link
Collaborator

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 20, 2022
@pritidesai
Copy link
Member Author

Pipelines WG - deleted v1alpha1 examples and tests but might happen with v1beta1. Closing this for now since havent seen this in a while. We can reopen if needed!

Repository owner moved this from Todo to Done in Pipelines V1 Nov 1, 2022
Repository owner moved this from Todo to Done in Tekton Community Roadmap Nov 1, 2022
@JeromeJu JeromeJu mentioned this issue Jun 15, 2023
Merged
4 tasks
@JeromeJu
Copy link
Member

seeing this in v1 examples twice at:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/flake Categorizes issue or PR as related to a flakey test lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
Pipelines V1
Status: Done
Tekton Community Roadmap
Status: Done
Milestone
No milestone
Development

No branches or pull requests
6 participants
@abayer @pritidesai @dibyom @jerop @JeromeJu @tekton-robot