Skip to content
This repository has been archived by the owner on Nov 28, 2022. It is now read-only.

🤖 Triggering CI on branch 'release-next' after synching to upstream/master #393

Closed
wants to merge 1 commit into from

Conversation

alanfx
Copy link

@alanfx alanfx commented Jan 13, 2020

No description provided.

@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jan 13, 2020
@openshift-ci-robot
Copy link

@alanfx: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws-ocp-42 46ccc55 link /test e2e-aws-ocp-42
ci/prow/4.3-e2e-aws-ocp-43 46ccc55 link /test 4.3-e2e-aws-ocp-43

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.

@matzew
Copy link
Member

matzew commented Jan 14, 2020

/close

@openshift-ci-robot
Copy link

@matzew: Closed this PR.

In response to this:

/close

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/test-infra repository.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/sync-fork-to-upstream size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants