Iván Valdés Castillo
Iván Valdés Castillo
We'll be removing release-3.5's test-smoke job. The [Makefile target](https://github.com/etcd-io/etcd/blob/2243367ddbf7aa1f2f7312234275ca8927defcfb/Makefile#L159) is the following: ```Makefile test-smoke: $(info log-file: test-$(TEST_SUFFIX).log) PASSES="fmt bom dep build unit" ./test.sh 2
Refer to https://github.com/kubernetes/test-infra/issues/32754#issuecomment-3014660991
X-posting https://github.com/etcd-io/etcd/pull/20116#issuecomment-2950067337, as we're having issues running 3.4 e2e tests on the Prow infra. > @joshjms, I can think of two solutions: > > 1. We run the tests on...
And now, with the activity, my comment keeps getting hidden. So, copying https://github.com/kubernetes/test-infra/issues/32754#issuecomment-2942746295 to the bottom to keep it visible. --- Because I don't have access to update the issue....
With all tasks completed, we have successfully migrated the Prow repository to etcd. Thanks for all your work, @joshjms and @abdurrehman107 :) /close
@jmhbnz, do we want to migrate jobs from branches other than `main` to prow? I haven't opened pull requests that run for 3.4/3.5 mainly because the `Makefile`s as stated above,...
Link to etcd-io/etcd#18173. Regardless of the previous comment and outcome. I think we're ready to drop the `optional: true` and tune the requested CPU/memory. I was going to do it...
We discussed this issue at the August 1st's etcd triage meeting. I'm just bumping this with a comment so we don't forget. @ArkaSaha30, do you have the capacity to do...
No worries, @ArkaSaha30. No rush at all. I was making sure that we didn't forget about this open issue.