Iván Valdés Castillo

Just giving an update that I have a [thread](https://kubernetes.slack.com/archives/CCK68P2Q2/p1724975407113939) in #sig-k8s-infra. It looks like the bug is in the infra, not the job itself.

Link to kubernetes/k8s.io#7241

The ARM issues are now solved. There are multiple green runs in prow (https://prow.k8s.io/job-history/gs/kubernetes-jenkins/logs/ci-etcd-robustness-arm64). @serathius, should we delete `ci-etcd-robustness-main-arm64` and only keep `ci-etcd-robustness-arm64`?

The difference between the jobs is that `ci-etcd-robustness-{amd64,arm64}` enables gofail `make gofail-enable` and builds the project (`make build`). While ci-etcd-robustness-main-{amd64,arm64}` doesn't. * `ci-etcd-robustness-arm64`: https://github.com/kubernetes/test-infra/blob/cb419f072809b7554602219dadee3b0433b5682d/config/jobs/etcd/etcd-periodics.yaml#L171-L183 ``` result=0 apt-get -o APT::Update::Error-Mode=any update...

The GitHub workflows we used to have didn't enable gofail, nor were we building the project. We should keep `ci-etcd-robustness-main-{arm64,amd64}`, which are already consistent with the job naming you suggested.

I believe the only outstanding task from this issue is marking the pre-submit jobs as blocking. @serathius, do you think we should do this soon, or should we leave them...

/cc @ahrtr

This is now irrelevant, as it will get replaced by further release automation.

We currently have four common groups of targets: 1. Test targets (`test-*`) 2. Build targets (`build-*`) 3. Static check targets (`verify-*`) 4. Static check autofix targets (`fix-*`) We also have...

@Himanshu-370, I was planning to do this, but working on other tasks related to the Go workspace has consumed most of my time. You could definitely help if we follow...