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.

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

feat: add test-name param to quality-dashboard task #866

Merged
merged 1 commit into from
Sep 10, 2024

Conversation

flacatus
Copy link
Contributor

Maintainers will complete the following section

Signed-off-by: Flavius Lacatusu <flacatus@redhat.com>
Copy link
Collaborator

@dirgim dirgim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dirgim
Copy link
Collaborator

dirgim commented Sep 10, 2024

/retest

Copy link

openshift-ci bot commented Sep 10, 2024

🚨 Error occurred while running the E2E tests, list of failed Spec(s):

  • ➡️ [failed] [It] [integration-service-suite Gitlab Status Reporting of Integration tests] Gitlab with status reporting of Integration tests in the assosiated merge request when a new Component with specified custom branch is created triggers a Build PipelineRun [integration-service, gitlab-status-reporting, custom-branch]
Timed out after 600.001s.
timed out when waiting for the build PipelineRun to start for the component gitlab-rep-oybz-tenant/test-comp-pac-gitlab-otmlnd
Expected success, but got an error:
    <*errors.errorString | 0xc000db8a80>: 
    no pipelinerun found for component test-comp-pac-gitlab-otmlnd
    {
        s: "no pipelinerun found for component test-comp-pac-gitlab-otmlnd",
    }

🙈 Link to Pod logs.
🙉 Link to Custom Resources.
🙊 Link to junit-summary.html.


@flacatus: 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/integration-service-e2e d39d06c link true /test integration-service-e2e

Full PR test history. Your PR dashboard.

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.

@kasemAlem
Copy link
Contributor

I do see a pipelineRuns in artifact
two of PLRs in the namespace/component gitlab-rep-oybz-tenant/test-comp-pac-gitlab-otmlnd in conditions reported succeeded while in status ITS is on Pending :

"test.appstudio.openshift.io/status": "[{\"scenario\":\"my-integration-test-fcox\",\"status\":\"Pending\",\"lastUpdateTime\":\"2024-09-10T16:22:16.139179535Z\",\"details\":\"Pending\"},{\"scenario\":\"my-integration-test-ozvi\",\"status\":\"Pending\",\"lastUpdateTime\":\"2024-09-10T16:22:16.139180535Z\",\"details\":\"Pending\"}]"

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants