[ https://issues.apache.org/jira/browse/BEAM-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15972105#comment-15972105 ]
Pablo Estrada commented on BEAM-1986: ------------------------------------- Are tests running in parallel here? If they are running in parallel, then a 1-second delay should not fix this issue, as two job names may still be generated at the same second (just one second later : ). So I agree that a random component or a more fine-grained time unit should help reduce this issue. > Job ALREADY_EXISTS in post commit > --------------------------------- > > Key: BEAM-1986 > URL: https://issues.apache.org/jira/browse/BEAM-1986 > Project: Beam > Issue Type: Bug > Components: sdk-py > Reporter: Ahmet Altay > Assignee: Mark Liu > Priority: Minor > > 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. -- This message was sent by Atlassian JIRA (v6.3.15#6346)