Update prow apps that use Git

[upodroid]

Follow up to https://github.com/kubernetes/test-infra/pull/29130

/cc @aojea

 REDACTED  C02CW0CDP3YY  ~  Desktop  Git  test-infra   master  $  gcrane ls gcr.io/k8s-prow/git | grep 2023
gcr.io/k8s-prow/git:v20230324-76cde35b3d
gcr.io/k8s-prow/git:v20230111-cd1b3caf9c
 REDACTED  C02CW0CDP3YY  ~  Desktop  Git  test-infra   master  $  gcrane ls gcr.io/k8s-prow/git-custom-k8s-auth | grep 2023
gcr.io/k8s-prow/git-custom-k8s-auth:v20230307-5398de3144
gcr.io/k8s-prow/git-custom-k8s-auth:v20230324-76cde35b3d

[ameukam]

Thanks!

/lgtm /approve

[upodroid]

/retest

Looks like a flake

[qaifshaikh]

/retest

[qaifshaikh]

Doesn't seem flaky

[qaifshaikh]

i think https://github.com/kubernetes/test-infra/pull/29133 needs to merge and we should have all the deploys working with the same images but newer versions

[upodroid]

 REDACTED  C02CW0CDP3YY  ~  Desktop  Git  test-infra   bump-base-images  ERROR  $  VERSION=dev ko build --local k8s.io/test-infra/prow/cmd/clonerefs
2023/03/24 11:26:17 Using base gcr.io/k8s-prow/git:v20230324-76cde35b3d@sha256:e0a930a0dc163deb2e3e68242dcbdf682a4c023c85dc5a25bd900691a83c5323 for k8s.io/test-infra/prow/cmd/clonerefs
2023/03/24 11:26:17 Using build config clonerefs for k8s.io/test-infra/prow/cmd/clonerefs
2023/03/24 11:26:17 Building k8s.io/test-infra/prow/cmd/clonerefs for linux/amd64
2023/03/24 11:26:23 Loading ko.local/clonerefs-143ec054fe7806d630542dbf80928171:ecd769a8403bcb6063baaaf4c8c0e2ab216adee0692f7582c78cdb486396ad23
2023/03/24 11:26:28 Loaded ko.local/clonerefs-143ec054fe7806d630542dbf80928171:ecd769a8403bcb6063baaaf4c8c0e2ab216adee0692f7582c78cdb486396ad23
2023/03/24 11:26:28 Adding tag latest
2023/03/24 11:26:28 Added tag latest
ko.local/clonerefs-143ec054fe7806d630542dbf80928171:ecd769a8403bcb6063baaaf4c8c0e2ab216adee0692f7582c78cdb486396ad23

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[dims]

/lgtm /approve /skip

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ameukam, dims, upodroid

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:

• ~~OWNERS~~ [ameukam,dims]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[aojea]

the failure seems legit

Unexpected error running \"go build\": exit status 2\ngo: unsupported GOOS/GOARCH pair unknown/unknown\n2023/03/24 19:26:36 Unexpected error running \"go build\": exit status 2\ngo: unsupported GOOS/GOARCH pair unknown/unknown\n2023/03/24 19:26:36 Unexpected error running \"go build\": exit status 2\ngo: unsupported

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[upodroid]

/hold

No point running failed tests over the weekend

[ameukam]

I think you are facing https://github.com/ko-build/ko/pull/975

[dims]

/test pull-test-infra-prow-image-build-test

[k8s-ci-robot]

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

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-ci-robot]

@upodroid: 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-test-infra-prow-image-build-test	1b74684197678a2562315ab0369a06da08d20a2d	link	true	/test pull-test-infra-prow-image-build-test
pull-test-infra-misc-image-build-test	1b74684197678a2562315ab0369a06da08d20a2d	link	true	/test pull-test-infra-misc-image-build-test

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.

[upodroid]

Closing as prow moved to its own repo