See <https://ci-builds.apache.org/job/Tomee/job/master-build-full-tck/603/display/redirect?page=changes>
Changes: [github] Update the systemd service example (#3085) [github] Register the MP-JWT filter only for the MP-JWT auth method (#3067) [github] Resolve MP-JWT security constraints per resource class (#3068) [github] Log webapp jars skipped by the scan exclusion list (#3069) [github] Do not map the caller principal to a role by name in getLogicalRoles (#3070) [github] Keep Debian package configuration read-only for the service group (#3071) [github] Bind the LiveReload connector to loopback and check the websocket origin (#3072) [github] Validate stored parameters in TomEEPbkdf2PasswordHash (#3073) [github] Verify Tomcat user identity store passwords with the realm CredentialHandler (#3074) [github] Make only_from authoritative for server services (#3075) [github] Warn that the Static3DES password cipher only obfuscates (#3076) [github] Passivate stateful beans to a private directory by default (#3077) [github] Warn when tomee-maven-plugin sends credentials over plain HTTP (#3078) [github] Reject archive entries escaping the target in tomee-maven-plugin (#3079) [github] TOMEE-4729 - Restore MP-JWT security state for asynchronous requests (#3080) [github] Keep RAFPassivater files in a private temp directory (#3082) [github] Do not return EJB exception messages from the default JAX-RS mapper (#3083) [github] Clear the WS-Security caller identity after the JAX-WS request (#3084) [github] Require a secret for stop requests on the admin port (#3087) ------------------------------------------ Started by upstream project "Tomee/master-sanity-checks" build number 1305 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 Cloning the remote Git repository Cloning repository https://github.com/apache/tomee > git init > <https://ci-builds.apache.org/job/Tomee/job/master-build-full-tck/ws/> # > 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 config remote.origin.url https://github.com/apache/tomee # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # > timeout=10 Avoid second fetch > git rev-parse refs/remotes/origin/main^{commit} # timeout=10 Checking out Revision 0fb057efe6e322538a8c30ddfa7401a4c0835793 (refs/remotes/origin/main) > git config core.sparsecheckout # timeout=10 > git checkout -f 0fb057efe6e322538a8c30ddfa7401a4c0835793 # timeout=10 Commit message: "Require a secret for stop requests on the admin port (#3087)" > git rev-list --no-walk fca9dbddff1d704d03bcfc77bf8e90e3a9aa24f6 # timeout=10 [master-build-full-tck] $ /bin/sh -xe /tmp/jenkins12117528864806524539.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
