Skip to content

[release-next] Use hacks directly #1100

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
wants to merge 3 commits into
base: release-next
Choose a base branch
from

Conversation

cardil
Copy link
Member

@cardil cardil commented Feb 14, 2025

/kind cleanup

Copy link

openshift-ci bot commented Feb 14, 2025

@cardil: The label(s) kind/cleanup cannot be applied, because the repository doesn't have them.

In response to this:

/kind cleanup

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.

Copy link

openshift-ci bot commented Feb 14, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: cardil
Once this PR has been reviewed and has the lgtm label, please assign matejvasek for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@cardil
Copy link
Member Author

cardil commented Feb 14, 2025

/cherrypick release-v1.17
/cherrypick release-v1.16
/cherrypick release-v1.15
/cherrypick main

@openshift-cherrypick-robot

@cardil: once the present PR merges, I will cherry-pick it on top of main, release-v1.15, release-v1.16, release-v1.17 in new PRs and assign them to you.

In response to this:

/cherrypick release-v1.17
/cherrypick release-v1.16
/cherrypick release-v1.15
/cherrypick main

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.

@codecov-commenter
Copy link

codecov-commenter commented Feb 14, 2025

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 64.45%. Comparing base (8765218) to head (1d04e5c).
Report is 470 commits behind head on release-next.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@                Coverage Diff                @@
##           release-next    #1100       +/-   ##
=================================================
+ Coverage         48.98%   64.45%   +15.47%     
=================================================
  Files                96      132       +36     
  Lines             13105    15678     +2573     
=================================================
+ Hits               6419    10105     +3686     
+ Misses             6049     4583     -1466     
- Partials            637      990      +353     
Flag Coverage Δ
e2e-test 36.31% <ø> (?)
e2e-test-runtime-go 26.29% <ø> (?)
e2e-test-runtime-node 25.70% <ø> (?)
e2e-test-runtime-python 25.70% <ø> (?)
e2e-test-runtime-quarkus 25.85% <ø> (?)
e2e-test-runtime-rust 24.78% <ø> (?)
e2e-test-runtime-springboot 24.84% <ø> (?)
e2e-test-runtime-typescript 25.81% <ø> (?)
integration-tests 51.63% <ø> (?)
unit-tests 50.59% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@serverless-qe serverless-qe force-pushed the release-next branch 7 times, most recently from 220451e to 02c86f8 Compare February 21, 2025 00:55
@openshift-merge-robot
Copy link

PR needs rebase.

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.

@gauron99
Copy link

the failing podman test can be resolved in following fashion: knative#2692 (fix for upstream)

@serverless-qe serverless-qe force-pushed the release-next branch 6 times, most recently from c0538b9 to 67e0987 Compare March 2, 2025 00:51
@serverless-qe serverless-qe force-pushed the release-next branch 8 times, most recently from d34e61d to 8184c8b Compare June 1, 2025 00:56
@serverless-qe serverless-qe force-pushed the release-next branch 7 times, most recently from 08c8044 to 606cec6 Compare June 8, 2025 00:58
@serverless-qe serverless-qe force-pushed the release-next branch 7 times, most recently from 7ebec07 to 6ae21e5 Compare June 15, 2025 01:02
@serverless-qe serverless-qe force-pushed the release-next branch 6 times, most recently from 62f99ee to 20d2f75 Compare June 22, 2025 00:59
@serverless-qe serverless-qe force-pushed the release-next branch 2 times, most recently from f2d8456 to d386ca0 Compare June 24, 2025 01:01
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants