Closed Prucek closed 6 months ago
Hi @Prucek. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
Name | Link |
---|---|
Latest commit | bca239a039f04dc0fe2003673633238bad70835b |
Latest deploy log | https://app.netlify.com/sites/k8s-prow/deploys/664c92aee8dc75000898923e |
Deploy Preview | https://deploy-preview-158--k8s-prow.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
/ok-to-test
FYI these are the failures we saw (and why I reverted the PR):
https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_prow/155/pull-prow-integration/1791473589053034496 https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_prow/155/pull-prow-integration/1791466104812474368
2024-05-17T13:58:28.169262008Z stderr F {"branch":"master","component":"gangway","error":"got 400 response","file":"sigs.k8s.io/prow/pkg/gangway/gangway.go:935","func":"sigs.k8s.io/prow/pkg/gangway.(*postsubmitJobHandler).getProwJobSpec","level":"info","msg":"Failed to get postsubmits from inrepoconfig","org":"org1","orgRepo":"org1/repo1","repo":"repo1","severity":"info","time":"2024-05-17T13:58:28Z"}
I have been looking at the gangway logs in the integration test, and I see the error comes from postsubmits I guess
But it is hard to look for the error because locally it didn't occur to me not even once
PR needs rebase.
@Prucek: The following tests failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
pull-prow-image-build-test | d07157db1b12ef19c40e0856caacae8bef922644 | link | true | /test pull-prow-image-build-test |
pull-prow-integration | d07157db1b12ef19c40e0856caacae8bef922644 | link | true | /test pull-prow-integration |
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.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Prucek
The full list of commands accepted by this bot can be found here.
I didn't close it, it closed on its own
@Prucek That's a fun little GitHub quirk. You have force pushed the bca239a commit to be the tip of this PR:
Prucek force-pushed the revert-156-revert-116-mass-job-status-change-api branch from d07157d to bca239a
Now, bca239a is the commit that was merged as a tip of the original (reverted) PR #116: https://github.com/kubernetes-sigs/prow/pull/116/commits
Which means this PR #158 would be a duplicate of an already closed PR #116 and therefore GitHub closes it too (normally this can happen when you have two open PRs trying to merge identical set of commits - once one of them merges, GitHub closes the other as well).
@petr-muller thanks for the explanation, now it makes sense
Reverts kubernetes-sigs/prow#156