https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-maven-hadoop-2.7/ https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-maven-hadoop-2.7-ubuntu-testing/ https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-maven-hadoop-3.2/ https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-maven-hadoop-3.2-jdk-11/
spark-master-test-maven-hadoop-3.2 looks like it's been timing out for ~2 weeks, but the others only for a few days. all of these builds have a 335 minute (5 hours, 35 mins) timeout configured. honestly, i feel that 5.5 hours is already an insane amount of time for these builds to run... do we need to increase it? can someone(s) here figure out what's taking so long and refactor some of the tests? shane -- Shane Knapp UC Berkeley EECS Research / RISELab Staff Technical Lead https://rise.cs.berkeley.edu --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
