Skip to content

Conversation

@chrischdi
Copy link
Member

What this PR does / why we need it:

Adds a junit file so test failures like ci connectivity can be analyzed using k8s-triage too.

/hold

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 11, 2025
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Nov 11, 2025
@chrischdi chrischdi force-pushed the pr-ci-junit-for-e2e-sh branch 5 times, most recently from 0388064 to 4b61c1a Compare November 12, 2025 07:21
@chrischdi
Copy link
Member Author

@chrischdi chrischdi force-pushed the pr-ci-junit-for-e2e-sh branch from 4b61c1a to 1b91f53 Compare November 12, 2025 07:24
@chrischdi chrischdi changed the title 🌱 hack/e2e.sh create a junit file when running e2e.sh [WIP] 🌱 hack/e2e.sh create a junit file when running e2e.sh Nov 12, 2025
@k8s-ci-robot k8s-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 12, 2025
@chrischdi chrischdi force-pushed the pr-ci-junit-for-e2e-sh branch 3 times, most recently from 8ea6b26 to 475c8a6 Compare November 12, 2025 07:51
@chrischdi chrischdi force-pushed the pr-ci-junit-for-e2e-sh branch 2 times, most recently from a4cd935 to aeb1a37 Compare November 12, 2025 09:54
@chrischdi
Copy link
Member Author

@k8s-ci-robot k8s-ci-robot changed the title [WIP] 🌱 hack/e2e.sh create a junit file when running e2e.sh 🌱 hack/e2e.sh create a junit file when running e2e.sh Nov 12, 2025
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 12, 2025
@chrischdi
Copy link
Member Author

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 13, 2025
@chrischdi chrischdi force-pushed the pr-ci-junit-for-e2e-sh branch from 263c2ef to c658619 Compare November 13, 2025 13:20
@chrischdi
Copy link
Member Author

/hold

To manually check result.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 13, 2025
@sbueringer
Copy link
Member

Thx!

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 13, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: dcb37c5d99c8d614feaaa7d70b236cd00e58b6ce

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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

The pull request process is described here

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 13, 2025
@chrischdi
Copy link
Member Author

/hold cancel

Happy path works too

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 13, 2025
@k8s-ci-robot k8s-ci-robot merged commit 54aab6f into kubernetes-sigs:main Nov 13, 2025
17 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.15 milestone Nov 13, 2025
@sbueringer
Copy link
Member

/cherry-pick release-1.14

@sbueringer
Copy link
Member

/cherry-pick release-1.13

@sbueringer
Copy link
Member

/cherry-pick release-1.12

@k8s-infra-cherrypick-robot

@sbueringer: new pull request created: #3673

In response to this:

/cherry-pick release-1.14

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.

@k8s-infra-cherrypick-robot

@sbueringer: new pull request created: #3674

In response to this:

/cherry-pick release-1.13

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.

@k8s-infra-cherrypick-robot

@sbueringer: #3670 failed to apply on top of branch "release-1.12":

Patch is empty.
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To record the empty patch as an empty commit, run "git am --allow-empty".
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"

In response to this:

/cherry-pick release-1.12

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.

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

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants