On Wed, 2014-09-24 at 12:19 +0100, Robbie Gemmell wrote:
The tests are now running again, but a couple of the URL tests still seem
to be failing on the CI job:
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-proton-j/lastBuild/org.apache.qpid$proton-tests/testReport/
They are all
On 25 September 2014 15:00, Alan Conway acon...@redhat.com wrote:
On Wed, 2014-09-24 at 12:19 +0100, Robbie Gemmell wrote:
The tests are now running again, but a couple of the URL tests still seem
to be failing on the CI job:
On Thu, 2014-09-25 at 15:59 +0100, Robbie Gemmell wrote:
On 25 September 2014 15:00, Alan Conway acon...@redhat.com wrote:
On Wed, 2014-09-24 at 12:19 +0100, Robbie Gemmell wrote:
The tests are now running again, but a couple of the URL tests still seem
to be failing on the CI job:
Failing in a different way now, the overall run of the python tests bombs
out. I see the same thing locally, where it was working when I made the
commit immediately before yours :)
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-proton-j/683/console
Running
Hum, CI is still broken.
https://builds.apache.org/job/Qpid-proton-j/org.apache.qpid
$proton-tests/683/testReport/org.apache.qpid.proton/JythonTest/test/
Somehow my trivial re-org of the URL tests in python has caused the
entire Jython test harness to explode in flight. It works fine on my box
This is also failing for me when I run the entire mvn install (after a mvn
clean).. it's not just on the CI for me
On Sep 25, 2014, at 2:20 PM, Robbie Gemmell robbie.gemm...@gmail.com wrote:
Failing in a different way now, the overall run of the python tests bombs
out. I see the same thing
On Thu, 2014-09-25 at 19:20 +0100, Robbie Gemmell wrote:
Failing in a different way now, the overall run of the python tests bombs
out. I see the same thing locally, where it was working when I made the
commit immediately before yours :)
Sorry, I had gone out by the time you mailed. I wasn't clear in my earlier
mail in that the local test I did was just in my normal env using Java8,
not the old one I dug out using Java 6. Installing an old version of Java
is easy enough though. I see you have fixed it and it wasnt related to the
The tests are now running again, but a couple of the URL tests still seem
to be failing on the CI job:
https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-proton-j/lastBuild/org.apache.qpid$proton-tests/testReport/
As mentioned in my other post about a timeline for dropping Java6 support,
they
