See <https://ci-builds.apache.org/job/Mesos/job/Mesos-Buildbot-ARM/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=--verbose%20--disable-libtool-wrappers%20--disable-java%20--disable-python%20--disable-parallel-test-execution,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1%20%20MESOS_TEST_AWAIT_TIMEOUT=60secs%20JOBS=16%20GTEST_FILTER=-DiskQuotaTest.SlaveRecovery,label_exp=mesos-arm/50/display/redirect?page=changes>
Changes: [cf.natali] Fixed stout cpplint errors. ------------------------------------------ Started by upstream project "Mesos/Mesos-Buildbot-ARM" build number 50 originally caused by: Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on mesos-arm1 (mesos-arm) in workspace <https://ci-builds.apache.org/job/Mesos/job/Mesos-Buildbot-ARM/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=--verbose%20--disable-libtool-wrappers%20--disable-java%20--disable-python%20--disable-parallel-test-execution,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1%20%20MESOS_TEST_AWAIT_TIMEOUT=60secs%20JOBS=16%20GTEST_FILTER=-DiskQuotaTest.SlaveRecovery,label_exp=mesos-arm/ws/> The recommended git tool is: git No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://gitbox.apache.org/repos/asf/mesos.git # > timeout=10 Using shallow fetch with depth 1 Fetching upstream changes from https://gitbox.apache.org/repos/asf/mesos.git > git --version # timeout=10 > git --version # 'git version 2.17.1' > git fetch --tags --progress --depth=1 -- > https://gitbox.apache.org/repos/asf/mesos.git > +refs/heads/*:refs/remotes/origin/* # timeout=60 Checking out Revision c8960288d2af25ccfc85550108c74875c363aef6 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f c8960288d2af25ccfc85550108c74875c363aef6 # timeout=10 Commit message: "Fixed stout cpplint errors." > git rev-list --no-walk 52cfb8ed0f3b48cadc90b7c15236c4c7e5489dd7 # timeout=10 [mesos-arm] $ /bin/sh -xe /tmp/jenkins1550612743362857516.sh + export OS=ubuntu-18.04-arm + export CTEST_OUTPUT_ON_FAILURE=1 + export JOBS=48 + time ./support/mesos-build.sh ./support/mesos-build.sh: line 42: docker: command not found Command exited with non-zero status 127 0.00user 0.00system 0:00.01elapsed 120%CPU (0avgtext+0avgdata 5996maxresident)k 0inputs+0outputs (0major+926minor)pagefaults 0swaps Build step 'Execute shell' marked build as failure Recording test results ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found. Configuration error?
