dannycranmer edited a comment on pull request #16513: URL: https://github.com/apache/flink/pull/16513#issuecomment-901126604
@hhkkxxx133 looks like the e2e test is failing because it is trying to pull into the `2.11` run. As seen in the maven command: ``` 2021-08-17T21:01:47.7373155Z Aug 17 21:01:47 Invoking mvn with '/home/vsts/maven_cache/apache-maven-3.2.5/bin/mvn -Dmaven.wagon.http.pool=false --settings /home/vsts/work/1/s/tools/ci/google-mirror-settings.xml -Dorg.slf4j.simpleLogger.showDateTime=true -Dorg.slf4j.simpleLogger.dateTimeFormat=HH:mm:ss.SSS -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn --no-snapshot-updates -B -Dhadoop.version=2.8.3 -Dinclude_hadoop_aws -Dscala-2.11 -Dflink.forkCount=2 -Dflink.forkCountTestPackage=2 -Dfast -Pskip-webui-build -Dlog.dir=/home/vsts/work/_temp/debug_files -DlogBackupDir=/home/vsts/work/_temp/debug_files -Dlog4j.configurationFile=file:///home/vsts/work/1/s/flink-end-to-end-tests/../tools/ci/log4j.properties -Dhadoop.version=2.8.3 -Dinclude_hadoop_aws -Dscala-2.11 -Pe2e-travis1 -Pe2e-travis2 -Pe2e-travis3 -Pe2e-travis4 -Pe2e-travis5 -Pe2e-travis6 verify -pl flink-end-to-end-tests/flink-batch-sql-test,flink-end-to-end-tests/flink-cli-test,flink -end-to-end-tests/flink-confluent-schema-registry,flink-end-to-end-tests/flink-connector-gcp-pubsub-emulator-tests,flink-end-to-end-tests/flink-dataset-allround-test,flink-end-to-end-tests/flink-dataset-fine-grained-recovery-test,flink-end-to-end-tests/flink-datastream-allround-test,flink-end-to-end-tests/flink-distributed-cache-via-blob-test,flink-end-to-end-tests/flink-elasticsearch5-test,flink-end-to-end-tests/flink-elasticsearch6-test,flink-end-to-end-tests/flink-elasticsearch7-test,flink-end-to-end-tests/flink-end-to-end-tests-common,flink-end-to-end-tests/flink-end-to-end-tests-common-kafka,flink-end-to-end-tests/flink-end-to-end-tests-hbase,flink-end-to-end-tests/flink-file-sink-test,flink-end-to-end-tests/flink-glue-schema-registry-avro-test,flink-end-to-end-tests/flink-glue-schema-registry-json-test,flink-end-to-end-tests/flink-heavy-deployment-stress-test,flink-end-to-end-tests/flink-high-parallelism-iterations-test,flink-end-to-end-tests/flink-local-recovery-and-allocatio n-test,flink-end-to-end-tests/flink-metrics-availability-test,flink-end-to-end-tests/flink-metrics-reporter-prometheus-test,flink-end-to-end-tests/flink-netty-shuffle-memory-control-test,flink-end-to-end-tests/flink-parent-child-classloading-test-lib-package,flink-end-to-end-tests/flink-parent-child-classloading-test-program,flink-end-to-end-tests/flink-plugins-test,flink-end-to-end-tests/flink-plugins-test/another-dummy-fs,flink-end-to-end-tests/flink-plugins-test/dummy-fs,flink-end-to-end-tests/flink-python-test,flink-end-to-end-tests/flink-queryable-state-test,flink-end-to-end-tests/flink-quickstart-test,flink-end-to-end-tests/flink-rocksdb-state-memory-control-test,flink-end-to-end-tests/flink-sql-client-test,flink-end-to-end-tests/flink-state-evolution-test,flink-end-to-end-tests/flink-stream-sql-test,flink-end-to-end-tests/flink-stream-state-ttl-test,flink-end-to-end-tests/flink-stream-stateful-job-upgrade-test,flink-end-to-end-tests/flink-streaming-kafka-test,flink-end-to-end -tests/flink-streaming-kafka-test-base,flink-end-to-end-tests/flink-streaming-kinesis-test,flink-end-to-end-tests/flink-tpcds-test,flink-end-to-end-tests/flink-tpch-test,,flink-walkthroughs/flink-walkthrough-common,flink-walkthroughs/flink-walkthrough-datastream-java,flink-walkthroughs/flink-walkthrough-datastream-scala, -DdistDir=/home/vsts/work/1/s/flink-dist/target/flink-1.14-SNAPSHOT-bin/flink-1.14-SNAPSHOT -Dcache-dir=/home/vsts/work/1/e2e_cache -Dcache-ttl=P3M -Dcache-download-attempt-timeout=4min -Dcache-download-global-timeout=10min' ``` Looks like the run command is generated [here](https://github.com/apache/flink/blob/master/flink-end-to-end-tests/run-nightly-tests.sh#L260) by the following: `e2e_modules=$(find flink-end-to-end-tests -mindepth 2 -maxdepth 5 -name 'pom.xml' -printf '%h\n' | sort -u | tr '\n' ',')` Since it is using a `find` it will always be picked up. Maybe you can change the `pom` to effectively be a no-op for `scala 2.11` somehow? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
