See 
<https://ci-builds.apache.org/job/Tomee/job/master-build-full-tck/605/display/redirect?page=changes>

Changes:

[github] TOMEE-4730 - Apply class-level security annotations of a resource 
superclass (#3081)

[github] make the scan exclusion and async MP-JWT tests independent of their 
environment (#3088)


------------------------------------------
Started by upstream project "Tomee/master-sanity-checks" build number 1306
originally caused by:
 Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on builds37 (ubuntu) in workspace 
<https://ci-builds.apache.org/job/Tomee/job/master-build-full-tck/ws/>
The recommended git tool is: NONE
No credentials specified
 > git rev-parse --resolve-git-dir 
 > <https://ci-builds.apache.org/job/Tomee/job/master-build-full-tck/ws/.git> # 
 > timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/apache/tomee # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
Fetching upstream changes from https://github.com/apache/tomee
 > git --version # timeout=10
 > git --version # 'git version 2.34.1'
 > git fetch --tags --force --progress -- https://github.com/apache/tomee 
 > +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/main^{commit} # timeout=10
Checking out Revision 1d72919b50ebd447fe839d9b9dfa36add82e206e 
(refs/remotes/origin/main)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1d72919b50ebd447fe839d9b9dfa36add82e206e # timeout=10
Commit message: "make the scan exclusion and async MP-JWT tests independent of 
their environment (#3088)"
 > git rev-list --no-walk 0fb057efe6e322538a8c30ddfa7401a4c0835793 # timeout=10
[master-build-full-tck] $ /bin/sh -xe /tmp/jenkins17954258413593034155.sh
+ /usr/local/asfpackages/maven/apache-maven-3.9.2/bin/mvn clean install 
-DskipTests
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-readable POM 
/home/jenkins/.m2/repository/org/apache/apache/40/apache-40.pom: input 
contained no data @ 
/home/jenkins/.m2/repository/org/apache/apache/40/apache-40.pom
 @ 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project org.apache.tomee:tomee-project:11.0.0-SNAPSHOT 
(<https://ci-builds.apache.org/job/Tomee/job/master-build-full-tck/ws/pom.xml)> 
has 1 error
[ERROR]     Non-readable POM 
/home/jenkins/.m2/repository/org/apache/apache/40/apache-40.pom: input 
contained no data @ 
/home/jenkins/.m2/repository/org/apache/apache/40/apache-40.pom
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
Build step 'Execute shell' marked build as failure
INFO: Processing JUnit
INFO: [JUnit] - No test report file(s) were found with the pattern 
'**/target/surefire-reports/TEST-*.xml' relative to 
'<https://ci-builds.apache.org/job/Tomee/job/master-build-full-tck/ws/'> for 
the testing framework 'JUnit'.
Did you enter a pattern relative to (and within) the workspace directory?
Did you generate the result report(s) for 'JUnit'?"
WARNING: All test reports are empty.
[Checks API] No suitable checks publisher found.
INFO: Setting the build status to SUCCESS

Reply via email to