XComp commented on code in PR #182: URL: https://github.com/apache/flink-docker/pull/182#discussion_r1508874814
########## .github/workflows/ci.yml: ########## @@ -17,14 +17,22 @@ name: "CI" on: [push, pull_request] +env: + TAR_URL: "https://s3.amazonaws.com/flink-nightly/flink-1.20-SNAPSHOT-bin-scala_2.12.tgz"; + jobs: ci: + name: CI using JDK ${{ matrix.java_version }} runs-on: ubuntu-latest + strategy: + fail-fast: false + max-parallel: 1 Review Comment: > My assumption is that I pushed another commit while another workflow was running and maybe they clashed on container name. But I tried to trigger several workflow runs, still could not reproduce the issue above. But my understanding is that jobs run on separate VMs which means that even if two jobs run in parallel starting a container with the same name would mean that they don't have any effect on each other. But I might be wrong here. :thinking: Can't we test that easily just starting a playground GHA workflow with two jobs where both start a container with the same name. If your claim is correct, we should see the same error appearing there. WDYT? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
