I have identified the source of my problem to be a failure of a copy
command run via maven-antrun-plugin. No error message was logged but copy
had failed as there were files owned by a different user than jenkins user
in the target directory of the copy. I was focusing on test failures (there
Looking at the log you provided, there appears to be a failure listed in
the summary table at the end. Perhaps that is the issue? (Note I don't use
Maven so not sure if that failure is "ok" or not)
Richard
On Wednesday, September 18, 2013, Farrukh Najmi wrote:
>
> I am new to Jenkins. I absolute
Thank guys for helping.
The JENKIS-19352 issue seems to result in false negatives. I am getting what
appears to be false positives.
Vincent Latombe wrote:
>Hi,
>
>this is probably yet another occurrence of
>https://issues.jenkins-ci.org/browse/JENKINS-19352 (since 1.526) . Try the
>same wit
Hi,
this is probably yet another occurrence of
https://issues.jenkins-ci.org/browse/JENKINS-19352 (since 1.526) . Try the
same with a freestyle job.
Vincent
2013/9/17 Farrukh Najmi
> That is the crux of the problem. The summary table shows a failure when
> nothing else in the log shows a fai
That is the crux of the problem. The summary table shows a failure when
nothing else in the log shows a failure. All junit tests pass and there
is no other indication in the verbose log of any other problem. Thus I
am perplexed as to what is going on. Could it be a bug in jenkins or a
plugin?
I am new to Jenkins. I absolutely love this software. Thank you Kohsuke and
friends. I have an issue for which I did not find an answer in archives.
I run jenkins 1.531 for my multi-module maven project. All tests in all
projects pass. There are no error or failures.
However, Jenkins persistent
