Home/ Questions/Q 8109443
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T01:25:11+00:00

Our unit tests failures are not being reported by Jenkins. Here’s what we see

  • 0

Our unit tests failures are not being reported by Jenkins. Here’s what we see in the build log:

[JENKINS] Recording test results
hudson.AbortException: Test reports were found but none of them are new. Did tests run? 
For example, /home/tomcat/.jenkins/jobs/ws-main-gerrit/workspace/commons/commons-utils/target/surefire-reports/TEST-commons.utils.TransformationUtilsTest.xml is 32 min old

The problem is that when the Jenkins build is triggered by Gerrit it creates the target directory with incorrect (30 minute old) timestamp. The time on the server where Jenkins and Gerrit reside is correct. When I login and do the maven build manually, it correctly reports the failures in the unit tests.

Any ideas what could cause the issue?
Thanks in advance!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The problem was that the NFS where Jenkins resides wasn’t using NTP (and was about 30 minutes behind) where the rest of the system was using it. So, that’s why the date command was returning the correct timestamp but the files in the target directory where created with the wrong timestamp.

    • 0