Skip to content

Conversation

@rh-tap-build-team
Copy link
Contributor

@rh-tap-build-team rh-tap-build-team bot commented Feb 2, 2026

@openshift-ci openshift-ci bot requested review from HozifaWasfy and querti February 2, 2026 22:04
@openshift-ci
Copy link

openshift-ci bot commented Feb 2, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rh-tap-build-team[bot]
Once this PR has been reviewed and has the lgtm label, please assign hozifawasfy for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@github-actions
Copy link
Contributor

github-actions bot commented Feb 2, 2026

🤖 Gemini AI Assistant Available

Hi @rh-tap-build-team[bot]! I'm here to help with your pull request. You can interact with me using the following commands:

Available Commands

  • @gemini-cli /review - Request a comprehensive code review

    • Example: @gemini-cli /review Please focus on security and performance
  • @gemini-cli <your question> - Ask me anything about the codebase

    • Example: @gemini-cli How can I improve this function?
    • Example: @gemini-cli What are the best practices for error handling here?

How to Use

  1. Simply type one of the commands above in a comment on this PR
  2. I'll analyze your code and provide detailed feedback
  3. You can track my progress in the workflow logs

Permissions

Only OWNER, MEMBER, or COLLABORATOR users can trigger my responses. This ensures secure and appropriate usage.


This message was automatically added to help you get started with the Gemini AI assistant. Feel free to delete this comment if you don't need assistance.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 2, 2026

🤖 Hi @rh-tap-build-team[bot], I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

@konflux-ci-qe-bot
Copy link

🤖 Pipeline Failure Analysis

Category: Timeout

The end-to-end tests timed out due to exceeding the allocated 2-hour execution limit, preventing the successful completion of the Prow job.

📋 Technical Details

Immediate Cause

The appstudio-e2e-tests/redhat-appstudio-e2e step exceeded its configured 2-hour timeout. The process was terminated after a 15-second grace period, indicating it did not complete within the allowed timeframe.

Contributing Factors

Analysis of additional context reveals several potential contributing factors. The build-service-controller-manager deployment is in a Degraded state, and numerous ArgoCD ApplicationSet resources are OutOfSync. Furthermore, TektonConfig and TektonAddon resources indicate that openshift console resources and the tkn-cli-serve deployment are not ready, suggesting underlying instability or unresponsiveness in the test environment infrastructure. These issues could have led to the extended test execution time.

Impact

The timeout failure prevented the completion of the end-to-end tests, thus blocking the Prow job and the verification of the infrastructure deployment for AppStudio. This means the changes associated with PR 10350 could not be validated by this job.

🔍 Evidence

appstudio-e2e-tests/redhat-appstudio-e2e

Category: timeout
Root Cause: The end-to-end tests failed because one of the processes exceeded the 2-hour execution timeout, indicating that the tests did not complete within the allocated time.

Logs:

artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step-log.txt line 1276
{"component":"entrypoint","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:169","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.ExecuteProcess","level":"error","msg":"Process did not finish before 2h0m0s timeout","severity":"error","time":"2026-02-03T00:07:05Z"}
artifacts/appstudio-e2e-tests/redhat-appstudio-e2e/step-log.txt line 1279
{"component":"entrypoint","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:267","func":"sigs.k8s.io/prow/pkg/entrypoint.gracefullyTerminate","level":"error","msg":"Process did not exit before 15s grace period","severity":"error","time":"2026-02-03T00:07:20Z"}

Analysis powered by prow-failure-analysis | Build: 2018445348736864256

@openshift-ci
Copy link

openshift-ci bot commented Feb 3, 2026

@rh-tap-build-team[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/appstudio-e2e-tests 23f528d link true /test appstudio-e2e-tests

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant