test(e2e): move flaky retry/matrix tests to no-ci temporarily#9242
Merged
tekton-robot merged 2 commits intotektoncd:mainfrom Dec 17, 2025
Merged
test(e2e): move flaky retry/matrix tests to no-ci temporarily#9242tekton-robot merged 2 commits intotektoncd:mainfrom
tekton-robot merged 2 commits intotektoncd:mainfrom
Conversation
- Add startupProbe to accommodate slow Docker daemon initialization - Allow up to 30 seconds for daemon startup before marking as failed - Verify daemon functionality with 'docker info' instead of cert existence - Tries to address flaky test failures in CI with k8s native sidecar support Signed-off-by: Vincent Demeester <[email protected]>
Move two consistently flaky e2e tests to no-ci to unblock CI while we investigate and fix the root cause: 1. pipelinerun-with-matrix - Times out at 900s on k8s-oldest + alpha 2. using-retries-and-retry-count-variables - Times out at 900s on k8s-oldest + alpha Both tests timeout at exactly 15 minutes (global test timeout) when running on k8s-oldest with alpha features enabled. The issue appears to be related to retry logic with matrix expansion or context variable substitution. Related to tektoncd#9201, tektoncd#9062
5 tasks
Member
Author
|
/kind flake |
Collaborator
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afrittoli The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This was referenced Dec 17, 2025
Member
Author
|
/cherry-pick release-v1.0.x |
Collaborator
|
✅ Cherry-pick to A new pull request has been created to cherry-pick this change to Please review and merge the cherry-pick PR. |
Closed
13 tasks
Member
Author
|
/cherry-pick release-v1.0.x |
Collaborator
vdemeester
added a commit
to vdemeester/tektoncd-pipeline
that referenced
this pull request
Jan 29, 2026
Add startupProbe with failureThreshold of 30 to allow more time for Docker daemon initialization. Change readinessProbe to use 'docker info' command which verifies the daemon is actually ready to accept commands. This is a cherry-pick of the probe changes from tektoncd#9242 on main.
8 tasks
tekton-robot
pushed a commit
that referenced
this pull request
Jan 30, 2026
Add startupProbe with failureThreshold of 30 to allow more time for Docker daemon initialization. Change readinessProbe to use 'docker info' command which verifies the daemon is actually ready to accept commands. This is a cherry-pick of the probe changes from #9242 on main.
Member
Author
|
/cherry-pick release-v1.0.x |
Collaborator
|
❌ Cherry-pick to The automatic cherry-pick to Output: Next steps:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Move two consistently flaky e2e tests to
no-ci/directory to unblock CI while we investigate and fix the root cause:pipelinerun-with-matrix (
examples/v1/pipelineruns/beta/pipelinerun-with-matrix.yaml)matrix-with-task-retriestask may have bug in context variable substitutionusing-retries-and-retry-count-variables (
examples/v1/pipelineruns/using-retries-and-retry-count-variables.yaml)Analysis
Both tests timeout at exactly 15 minutes (global test timeout in
test/wait.go:64) when running on k8s-oldest with alpha features enabled. The common pattern:Hypothesis: The retry logic with
$(context.pipelineTask.retries)or$(context.task.retry-count)may not work correctly on older Kubernetes versions with alpha features, causing infinite retry loops until timeout.Next Steps
Related
Closes #9201
Related to #9062
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes