https://travis-ci.org/ottobackwards/commons-vfs/builds/342485419

So this builds locally with mvn clean package, but fails in travis, anyone
familiar?


On February 16, 2018 at 14:23:31, Bernd Eckenfels (e...@zusammenkunft.net)
wrote:

There is something fishy going on with the way testdatan and Testsuites are
generated. It results in a lot of NPEs because the setConfig is not
properly called. One of the causes seem to be on the fly compilation by
concurrent IDEs, sometimes it is caused by not found test data (which makes
the setUp fail but not be logged cleanly). It’s a bit annoying, sorry. I
suspect that maven clean in the toplevel project cures some of them —
sometimes.

Gruss
Bernd
--
http://bernd.eckenfels.net
------------------------------
*From:* Otto Fowler <ottobackwa...@gmail.com>
*Sent:* Friday, February 16, 2018 8:18:44 PM
*To:* Gary Gregory; Commons Developers List
*Cc:* Bernd Eckenfels
*Subject:* Re: [VFS] trunk build failing in travis

That did the trick.  Thank you. I’m going to submit pr’s for VFS-398 and
VFS-614 soon.



On February 16, 2018 at 13:54:53, Gary Gregory (garydgreg...@gmail.com)
wrote:

Note that the Travis build is now green:
https://travis-ci.org/apache/commons-vfs/

Gary

On Fri, Feb 16, 2018 at 11:34 AM, Gary Gregory <garydgreg...@gmail.com>
wrote:

> Make sure you have the latest from trunk. The build works for me locally
> using 'mvn clean package' using Oracle Java 7 and 8:
>
> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> 2017-10-18T01:58:13-06:00)
> Maven home: C:\Java\apache-maven-3.5.2\bin\..
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_162\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> and
>
> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
> 2017-10-18T01:58:13-06:00)
> Maven home: C:\Java\apache-maven-3.5.2\bin\..
> Java version: 1.7.0_80, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_80\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"
>
> Gary
>
>
> On Fri, Feb 16, 2018 at 11:04 AM, Otto Fowler <ottobackwa...@gmail.com>
> wrote:
>
>> Any ideas on this?
>>
>> Even with the old pom, I’m seeing failures I cannot explain. I have a
>> couple of PR’s I think I’d like to submit, but building seems a bit of
>> mess.
>>
>>
>>
>> On February 15, 2018 at 22:03:06, Bernd Eckenfels (e...@zusammenkunft.net
>> )
>> wrote:
>>
>> Hello,
>>
>> I digged a bit deeper, and on my Windows System surefire 1.20.1 is
failing
>> because of this new „ping“ behavior:
>>
>> http://maven.apache.org/surefire/maven-surefire-plugin/
>> examples/shutdown.html
>>
>> Looks like a bug that surefire is not falling back when wmic is not found
>> (or better search for it), however after I fixed my PATH to include
>> c:\Windows\System32\wbem the new surefire also works. -> the downgrade is
>> wrong.
>>
>> Since I commited on the wrong tag again, can somebody rename it and copy
>> the Revision 1811361 from rc2 again?
>>
>>
>> Gruss
>> Bernd
>>
>
>

Reply via email to