See <https://ci-builds.apache.org/job/Allura/job/Allura-py3.7/1/display/redirect>
Changes: ------------------------------------------ Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on builds40 (ubuntu) in workspace <https://ci-builds.apache.org/job/Allura/job/Allura-py3.7/ws/> [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... The recommended git tool is: NONE No credentials specified Cloning the remote Git repository Cloning repository https://gitbox.apache.org/repos/asf/allura.git/ > git init <https://ci-builds.apache.org/job/Allura/job/Allura-py3.7/ws/> # > timeout=10 Fetching upstream changes from https://gitbox.apache.org/repos/asf/allura.git/ > git --version # timeout=10 > git --version # 'git version 2.17.1' > git fetch --tags --progress -- > https://gitbox.apache.org/repos/asf/allura.git/ > +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://gitbox.apache.org/repos/asf/allura.git/ > # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # > timeout=10 Avoid second fetch > git rev-parse refs/remotes/origin/python3.7^{commit} # timeout=10 > git rev-parse origin/python3.7^{commit} # timeout=10 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Recording test results ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error? Publishing Clover coverage report... No Clover report will be published due to a build Failure