You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2021/03/01 18:34:28 UTC
Build failed in Jenkins: Allura » Allura-py3 #19
See <https://ci-builds.apache.org/job/Allura/job/Allura-py3/19/display/redirect?page=changes>
Changes:
[dbrondsema] Handle better invalid URLs like /_list/ with no path after
------------------------------------------
[...truncated 20.50 KB...]
Successfully built pysvn
Installing collected packages: pysvn
Successfully installed pysvn-1.9.12
Looking up latest PySVN version...
Downloading PySVN 1.9.12...
Building PySVN...
PySVN is installed.
<https://ci-builds.apache.org/job/Allura/job/Allura-py3/ws/.allura-venv/lib/python3.6/site-packages/pycodestyle.py>:2623: UserWarning: [pep8] section is deprecated. Use [pycodestyle].
warnings.warn('[pep8] section is deprecated. Use [pycodestyle].')
# setting up Allura dependencies
/usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'message_extractors'
warnings.warn(msg)
warning: no files found matching 'allura/public/favicon.ico'
# setting up AlluraTest dependencies
# setting up ForgeActivity dependencies
# setting up ForgeBlog dependencies
# setting up ForgeChat dependencies
# setting up ForgeDiscussion dependencies
# setting up ForgeFeedback dependencies
# setting up ForgeGit dependencies
# setting up ForgeImporters dependencies
# setting up ForgeLink dependencies
# setting up ForgeShortUrl dependencies
# setting up ForgeSVN dependencies
# setting up ForgeTracker dependencies
# setting up ForgeUserStats dependencies
# setting up ForgeWiki dependencies
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated lodash-node@2.4.1: This package is discontinued. Use lodash@^4.0.0.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated exists-sync@0.0.4: Please replace with usage of fs.existsSync
npm WARN deprecated core-js@1.2.7: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated core-js@2.6.12: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
> node-sass@4.14.1 install <https://ci-builds.apache.org/job/Allura/job/Allura-py3/ws/node_modules/node-sass>
> node scripts/install.js
Cached binary found at /home/jenkins/.npm/node-sass/4.14.1/linux-x64-72_binding.node
> core-js@2.6.12 postinstall <https://ci-builds.apache.org/job/Allura/job/Allura-py3/ws/node_modules/core-js>
> node -e "try{require('./postinstall')}catch(e){}"
> node-sass@4.14.1 postinstall <https://ci-builds.apache.org/job/Allura/job/Allura-py3/ws/node_modules/node-sass>
> node scripts/build.js
Binary found at <https://ci-builds.apache.org/job/Allura/job/Allura-py3/ws/node_modules/node-sass/vendor/linux-x64-72/binding.node>
Testing binary
Binary is fine
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN foundation-sites@6.6.3 requires a peer of jquery@>=2.2.0 but none is installed. You must install peer dependencies yourself.
npm WARN foundation-sites@6.6.3 requires a peer of what-input@>=4.1.0 but none is installed. You must install peer dependencies yourself.
added 575 packages from 393 contributors and audited 576 packages in 67.684s
10 packages are looking for funding
run `npm fund` for details
found 38 vulnerabilities (12 low, 2 moderate, 23 high, 1 critical)
run `npm audit fix` to fix them, or `npm audit` for details
<DummyProcess(Thread-13, started daemon 140366904813312)> running `nosetests --with-xunitmp --processes=4 --process-timeout=360` in AlluraTest
<DummyProcess(Thread-10, started daemon 140367475222272)> running `nosetests allura/tests/ --with-xunitmp --processes=4 --process-timeout=360` in Allura
<DummyProcess(Thread-12, started daemon 140366913206016)> running `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeActivity
<DummyProcess(Thread-8, started daemon 140367492007680)> running `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeBlog
<DummyProcess(Thread-3, started daemon 140367740806912)> running `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeChat
<DummyProcess(Thread-16, started daemon 140366879635200)> running `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeDiscussion
<DummyProcess(Thread-2, started daemon 140367749199616)> running `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeFeedback
<DummyProcess(Thread-1, started daemon 140367757592320)> running `nosetests --with-xunitmp ` in ForgeGit
<DummyProcess(Thread-11, started daemon 140367466829568)> running `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeImporters
<DummyProcess(Thread-4, started daemon 140367732414208)> running `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeLink
<DummyProcess(Thread-7, started daemon 140367500400384)> running `nosetests --with-xunitmp ` in ForgeSVN
<DummyProcess(Thread-9, started daemon 140367483614976)> running `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeShortUrl
<DummyProcess(Thread-5, started daemon 140367517185792)> running `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeTracker
<DummyProcess(Thread-14, started daemon 140366896420608)> running `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeUserStats
<DummyProcess(Thread-6, started daemon 140367508793088)> running `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeWiki
<DummyProcess(Thread-15, started daemon 140366888027904)> running `npm run lint-es6` in .
> allura@0.0.0 lint-es6 <https://ci-builds.apache.org/job/Allura/job/Allura-py3/ws/>
> eslint -c .eslintrc-es6 --ignore-path .eslintignore-es6 Allura/allura/public/**/*.es6.js || true
finished `npm run lint-es6` in .
..........SSSSSSSSSSSSS......
----------------------------------------------------------------------
Ran 29 tests in 11.114s
OK (SKIP=13)
finished `nosetests --with-xunitmp --processes=4 --process-timeout=360` in AlluraTest
..
----------------------------------------------------------------------
Ran 2 tests in 13.002s
OK
finished `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeChat
...........
----------------------------------------------------------------------
Ran 11 tests in 20.131s
OK
finished `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeShortUrl
.............
----------------------------------------------------------------------
Ran 13 tests in 21.422s
OK
finished `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeFeedback
...................
----------------------------------------------------------------------
Ran 19 tests in 23.871s
OK
finished `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeLink
......................
----------------------------------------------------------------------
Ran 22 tests in 30.257s
OK
finished `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeActivity
............
----------------------------------------------------------------------
Ran 12 tests in 44.927s
OK
finished `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeUserStats
..................................................S.......
----------------------------------------------------------------------
Ran 58 tests in 54.271s
OK (SKIP=1)
finished `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeBlog
.................................................................S........
----------------------------------------------------------------------
Ran 74 tests in 72.749s
OK (SKIP=1)
finished `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeWiki
........................................................................
----------------------------------------------------------------------
Ran 72 tests in 91.256s
OK
finished `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeDiscussion
<https://ci-builds.apache.org/job/Allura/job/Allura-py3/ws/ForgeTracker/forgetracker/tests/functional/test_root.py>:916: UserWarning: No parser was explicitly specified, so I'm using the best available HTML parser for this system ("html5lib"). This usually isn't a problem, but if you run this code on another system, or in a different virtual environment, it may use a different parser and behave differently.
The code that caused this warning is on line 916 of the file <https://ci-builds.apache.org/job/Allura/job/Allura-py3/ws/ForgeTracker/forgetracker/tests/functional/test_root.py.> To get rid of this warning, pass the additional argument 'features="html5lib"' to the BeautifulSoup constructor.
file_link = BeautifulSoup(form.text).findAll('a')[2]
<https://ci-builds.apache.org/job/Allura/job/Allura-py3/ws/ForgeTracker/forgetracker/tests/functional/test_root.py>:959: UserWarning: No parser was explicitly specified, so I'm using the best available HTML parser for this system ("html5lib"). This usually isn't a problem, but if you run this code on another system, or in a different virtual environment, it may use a different parser and behave differently.
The code that caused this warning is on line 959 of the file <https://ci-builds.apache.org/job/Allura/job/Allura-py3/ws/ForgeTracker/forgetracker/tests/functional/test_root.py.> To get rid of this warning, pass the additional argument 'features="html5lib"' to the BeautifulSoup constructor.
download = self.app.get(str(BeautifulSoup(form.text).findAll('a')[2]['href']))
<https://ci-builds.apache.org/job/Allura/job/Allura-py3/ws/ForgeTracker/forgetracker/tests/functional/test_root.py>:1339: UserWarning: No parser was explicitly specified, so I'm using the best available HTML parser for this system ("html5lib"). This usually isn't a problem, but if you run this code on another system, or in a different virtual environment, it may use a different parser and behave differently.
The code that caused this warning is on line 1339 of the file <https://ci-builds.apache.org/job/Allura/job/Allura-py3/ws/ForgeTracker/forgetracker/tests/functional/test_root.py.> To get rid of this warning, pass the additional argument 'features="html5lib"' to the BeautifulSoup constructor.
error_message = BeautifulSoup(form.text).find('div', {'class': 'error'})
...........................................................................................................................................................................................................
----------------------------------------------------------------------
Ran 203 tests in 153.287s
OK
finished `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeTracker
..........................................................................................................................SSSS..SS..........S..S.
----------------------------------------------------------------------
Ran 145 tests in 174.614s
OK (SKIP=8)
finished `nosetests --with-xunitmp --processes=4 --process-timeout=360` in ForgeImporters
.......................................................................................
----------------------------------------------------------------------
Ran 87 tests in 218.048s
OK
finished `nosetests --with-xunitmp ` in ForgeSVN
..................................................................................................................................................................................................................................................................................................................................................S.............................................................................................................................................................................................................................................................................................SSSSSSSS.....................................................................................................................................................................................................S...............................................................................................................................................................................................................................................................................................................................................................................................
----------------------------------------------------------------------
Ran 1213 tests in 233.575s
OK (SKIP=10)
finished `nosetests allura/tests/ --with-xunitmp --processes=4 --process-timeout=360` in Allura
..........................................................................................................................................................
----------------------------------------------------------------------
Ran 154 tests in 272.251s
OK
finished `nosetests --with-xunitmp ` in ForgeGit
/p/test/wiki/_discuss/thread/1c7aa857e3/ 200 OK
{"ming": 81, "logging": 74, "jinja.compile": 17, "jinja": 1, "navbar": 1, "sidebar": 1, "markdown": 4}
npm: 6.14.11
hostname: asf944
NODE_NAME: H44
FATAL: Remote call on H44 failed
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to H44
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788)
at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
at hudson.remoting.Channel.call(Channel.java:998)
at hudson.Launcher$RemoteLauncher.kill(Launcher.java:1083)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:510)
at hudson.model.Run.execute(Run.java:1880)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:428)
java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins
at jenkins.agents.AgentComputerUtil.getChannelToMaster(AgentComputerUtil.java:48)
at hudson.util.ProcessTree.get(ProcessTree.java:432)
at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1100)
at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1091)
at hudson.remoting.UserRequest.perform(UserRequest.java:211)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused: java.io.IOException: Remote call on H44 failed
at hudson.remoting.Channel.call(Channel.java:1004)
at hudson.Launcher$RemoteLauncher.kill(Launcher.java:1083)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:510)
at hudson.model.Run.execute(Run.java:1880)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:428)
Recording test results
Publishing Clover coverage report...
Clover HTML report '<https://ci-builds.apache.org/job/Allura/job/Allura-py3/ws/'> does not exist and was not copied!
Clover XML file '**/coverage.xml' does not exist in '<https://ci-builds.apache.org/job/Allura/job/Allura-py3/ws/'> and was not copied!
Processing Clover XML report ...
Could not find '/**/coverage.xml'. Did you generate the XML report for Clover?
Jenkins build is back to normal : Allura » Allura-py3 #20
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://ci-builds.apache.org/job/Allura/job/Allura-py3/20/display/redirect?page=changes>