Build failed in Jenkins: Allura » Allura-py3.7 #8

[Apache Jenkins Server <je...@builds.apache.org>]

See <https://ci-builds.apache.org/job/Allura/job/Allura-py3.7/8/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...
[WS-CLEANUP] Done
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/master^{commit} # timeout=10
Checking out Revision 57eae8cd97880b61af0f471f4b875a339d942899 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 57eae8cd97880b61af0f471f4b875a339d942899 # timeout=10
Commit message: "Remove old force_ssl.logged_in config, which is the only situation a 302 Found would've been appropriate for http/https redirects"
First time build. Skipping changelog.
[Allura-py3.7] $ /bin/bash /tmp/jenkins6472977958129584445.sh
/tmp/jenkins6472977958129584445.sh: line 3: ./scripts/jenkins-python3.7.sh: No such file or directory
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?
Publishing Clover coverage report...
No Clover report will be published due to a build Failure

Jenkins build is back to normal : Allura » Allura-py3.7 #9

[Apache Jenkins Server <je...@builds.apache.org>]

See <https://ci-builds.apache.org/job/Allura/job/Allura-py3.7/9/display/redirect?page=changes>