Jenkins failure when no tests failed

[Farrukh Najmi]

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 persistently reports failure in the second last module in the build sequence. Tests Results page shows 0 failure as well.

A log is available here.

What might be the cause of this failure and how can I analyze this better?

--
Regards,
Farrukh Najmi

[Richard Bywater]

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

--
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 jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Farrukh Najmi]

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?

On 09/17/2013 03:04 PM, Richard Bywater wrote:

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 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 persistently reports failure in the second last module in the build sequence. Tests Results page shows 0 failure as well.

A log is available here.

What might be the cause of this failure and how can I analyze this better?

-- 
Regards,
Farrukh Najmi

Web: http://www.wellfleetsoftware.com

[Vincent Latombe]

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 <farruk...@gmail.com>

[Farrukh Najmi]

Thank guys for helping.

The JENKIS-19352 issue seems to result in false negatives. I am getting what appears to be false positives.

You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/d62Uyk0FgoA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.

[Farrukh Najmi]

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 were none) but realize now that maven build can fail outside of tests for any number of reasons (e.g. copy failure). The only question is why is the error message from copy failure not in the log.

This is what my log looks like (notice no copy error message):

     [copy] No sources found.
     [copy] Copying 1 file to /var/xxx/docroot/plugins
     [copy] Copying /var/lib/jenkins/workspace/xxx/target/xxx-4.14-SNAPSHOT.jar to /var/xxx/docroot/plugins/xxx-4.14-SNAPSHOT.jar
[BFA] Scanning build for known causes...

[BFA] Done. 0s


This is what my maven-antrun-plugin config looks like:

                    <plugin>
                        <artifactId>maven-antrun-plugin</artifactId>
                        <executions>
                            <execution>
                                <id>install-static-resources</id>
                                <phase>install</phase>
                                <configuration>
                                    <tasks>
                                        <mkdir dir="/var/xyz/docroot" />
                                        <unzip src="target/myproject-${project.version}.zip" dest="/var/xyz/docroot/" />
                                    </tasks>
                                </configuration>
                                <goals>
                                    <goal>run</goal>
                                </goals>
                            </execution>
                        </executions>
                    </plugin>