I noticed a job failed with ALREDY_EXISTS error, a sign of same job_name auto generated twice. Could we add a 1 second delay to prevent things like this?
https://builds.apache.org/view/Beam/job/beam_PostCommit_Python_Verify/1877/consoleFull
cc: [~pabloem] Another perspective, would it make sense to add a small random component (e.g. 1-2 digits) to job name to reduce this issue? Or perhaps include ms resolution.
Imported from Jira BEAM-1986. Original Jira may contain additional context.
Reported by: altay.
I noticed a job failed with ALREDY_EXISTS error, a sign of same
job_nameauto generated twice. Could we add a 1 second delay to prevent things like this?https://builds.apache.org/view/Beam/job/beam_PostCommit_Python_Verify/1877/consoleFull
cc: [~pabloem] Another perspective, would it make sense to add a small random component (e.g. 1-2 digits) to job name to reduce this issue? Or perhaps include ms resolution.
Imported from Jira BEAM-1986. Original Jira may contain additional context.
Reported by: altay.