On 09/06/15 12:30 -0400, Ken Giusti wrote:
A betting man would wager it has something to do with the recent changes to the 
python setup.py.

I'll have a look into it.

----- Original Message -----
From: "Gordon Sim" <g...@redhat.com>
To: proton@qpid.apache.org
Sent: Tuesday, June 9, 2015 11:57:25 AM
Subject: something rotten in the state of... something or other

I've recently started seeing errors[1] when running tests due to left
over artefacts of previous builds. This happens even for a completely
clean build directory, as some of the offending artefacts seem to be
created in the source tree.

Jython seems to be trying and failing to load cproton. With a completely
clean source and build tree, everything passes, but it is kind of
annoying to have to rely on that. Is anyone else seeing anything
similar? Any ideas as to the cause (I've only seen it happening quite
recently) or possible cures?

I haven't been able to replicate this but I'm afraid it might be my
fault. Does it happen to you every time?

Thanks,
Flavio



[1]:

> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Running org.apache.qpid.proton.InteropTest
> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.119 sec
> Running org.apache.qpid.proton.JythonTest
> 2015-06-09 16:49:29.705 INFO About to call Jython test script:
> '/home/gordon/projects/proton-git/tests/python/proton-test' with
> '/home/gordon/projects/proton-git/tests/python' added to Jython path
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.207 sec
> <<< FAILURE!
> test(org.apache.qpid.proton.JythonTest)  Time elapsed: 5.203 sec  <<<
> FAILURE!
> java.lang.AssertionError: Caught PyException on invocation number 2:
> Traceback (most recent call last):
>   File "/home/gordon/projects/proton-git/tests/python/proton-test", line
>   616, in <module>
>     m = __import__(name, None, None, ["dummy"])
>   File
>   "/home/gordon/projects/proton-git/tests/python/proton_tests/__init__.py",
>   line 20, in <module>
>     import proton_tests.codec
>   File
>   "/home/gordon/projects/proton-git/tests/python/proton_tests/codec.py",
>   line 20, in <module>
>     import os, common, sys
>   File
>   "/home/gordon/projects/proton-git/tests/python/proton_tests/common.py",
>   line 26, in <module>
>     from proton import Connection, Transport, SASL, Endpoint, Delivery, SSL
>   File
>   
"/home/gordon/projects/proton-git/tests/../proton-c/bindings/python/proton/__init__.py",
>   line 33, in <module>
>     from cproton import *
>   File
>   
"/home/gordon/projects/proton-git/tests/../proton-c/bindings/python/cproton.py",
>   line 29, in <module>
>     import _cproton
> ImportError: No module named _cproton
>  with message: null
>    at org.junit.Assert.fail(Assert.java:93)
>    at org.apache.qpid.proton.JythonTest.runTestOnce(JythonTest.java:120)
>    at org.apache.qpid.proton.JythonTest.test(JythonTest.java:95)
>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>    at
>    
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>    at
>    
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>    at java.lang.reflect.Method.invoke(Method.java:606)
>    at
>    
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>    at
>    
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>    at
>    
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>    at
>    
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>    at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
>    at
>    
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
>    at
>    
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
>    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
>    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
>    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
>    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
>    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
>    at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
>    at
>    
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
>    at
>    
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
>    at
>    
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>    at
>    
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>    at
>    
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>    at java.lang.reflect.Method.invoke(Method.java:606)
>    at
>    
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
>    at
>    
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
>    at
>    
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
>    at
>    
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
>    at
>    org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
>
>
> Results :
>
> Failed tests:   test(org.apache.qpid.proton.JythonTest): Caught PyException
> on invocation number 2: Traceback (most recent call last):(..)
>
> Tests run: 9, Failures: 1, Errors: 0, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] proton-project .................................... SUCCESS [1.207s]
> [INFO] proton-j .......................................... SUCCESS [2.310s]
> [INFO] proton-jms ........................................ SUCCESS [0.623s]
> [INFO] proton-hawtdispatch ............................... SUCCESS [1.558s]
> [INFO] proton-tests ...................................... FAILURE [5.737s]
> [INFO] proton-j-messenger-example ........................ SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 11.637s
> [INFO] Finished at: Tue Jun 09 16:49:34 BST 2015
> [INFO] Final Memory: 14M/163M
> [INFO]
> ------------------------------------------------------------------------


--
-K

--
@flaper87
Flavio Percoco

Attachment: pgpgcMhOBnocX.pgp
Description: PGP signature

Reply via email to