You're welcome! Such issues are very common when running integration tests.
I had similar problems running the Jersey build.
I wonder if it makes sense to fail early in such situations. Just checking
the most important ports before starting the container could help here.
Am Do., 22. März 2018 um 19:35 Uhr schrieb Stephane Epardaud <
Yeah, sorry, you guys are right, I had a lone `oc cluster` up on 8443
I didn't account for, I only checked that my 8080 port was free.
Thanks and sorry for the noise.
On 22/03/18 17:52, Alessio Soldano wrote:
Are you still having problems or managed to run the testsuite locally?
On Tue, Mar 20, 2018 at 1:06 PM, Stephane Epardaud <stef(a)epardaud.fr>
> Damn, that's pretty annoying because I don't know what could be the issue
> and most tests don't pass.
> Apache Maven 3.5.0
> Maven home: /usr/share/maven
> Java version: 1.8.0_151, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.13.0-31-generic", arch:
> I'm running it with `mvn clean install`
> On 20/03/18 12:54, Alessio Soldano wrote:
> Of course they run :-) Latest run on Travis CI against latest commit
> passed 23hrs ago, btw.
> How are you running the testsuite, which jdk and mvn version?
> On Tue, Mar 20, 2018 at 11:39 AM, Stephane Epardaud <stef(a)epardaud.fr>
>> I get lots of test failures where the clients can't be cleaned up
>> because they're null:
>> Do tests run on master for you?
>> resteasy-dev mailing list
> Alessio Soldano
> Associate Manager
> Red Hat
> resteasy-dev mailing list
resteasy-dev mailing list