I don't know if this helps, but...
* I've gone through the config.xml file and compared it to an old backup
that worked as expected - I can't see any differences that I can not
explain.
* I've also compared the config.xml files for a project that reports the
right number of tests and one that reports the wrong number. Obviously
there are differences, but I can't see anything that might be related to
the the way JUnit tests are reported.
* There is nothing in the Jenkins logs that indicates a problem with the
rogue project
* There are two lines in the console output that read:
[JENKINS] Recording test results
Although this was always the case
Is there some other place I should be looking to determine what the problem
might be?
On 8 June 2016 at 16:17, RDR <[email protected]> wrote:
> Hi,
>
> I've just upgraded from 1.559 to 2.8. There were a few oddities in the
> upgrade process which I've worked my way past, but there is one that has
> stumped me. For some (but not all) of my projects Jenkins is showing a 100%
> increase in the number of Unit tests. I'm surprised by this as I've not
> changed the code or modified the Jenkins job configuration.
>
> Is this a know issues? Is there any known work around?
>
> I've done a search through Google and don't see any other reports of this
> problem in the last few years.
>
> Cheers
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CAB9wPTRsDGMLrmKw6du%3D8r634CdOY%2Bw7TCqys1Bg%3DTSGFe9YHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
