[Buildroot] [RFC] testing: add python-crossbar tests

Ricardo Martincoski ricardo.martincoski at gmail.com
Tue Sep 18 02:31:23 UTC 2018


Hello,

On Mon, Sep 17, 2018 at 10:55 AM, Thomas Petazzoni wrote:

> On Thu, 15 Feb 2018 23:16:32 -0200, Ricardo Martincoski wrote:
> 
>> On Thu, Feb 15, 2018 at 11:41 AM, Yegor Yefremov wrote:
>> 
>> [snip]
>> > 
>> > I've tried this test locally, but it always timeouts. Even if I
>> > specify an hour as a timeout.  
>> 
>> I confirm that here, both test cases fail by timeout, so it should not be
>> related to the host.

At the time I confirmed with the patch applied on aa77030b8f and also on
(aa77030b8f +
 http://patchwork.ozlabs.org/patch/874421/ +
 http://patchwork.ozlabs.org/patch/874422/ )
and I got the timeout in both cases.

> 
> I applied Yegor's patch, and ran he test. It doesn't time out here.
> Here is what I have in the TestPythonPy2Crossbar-run.log:
> 
> Welcome to Buildroot
> buildroot login: root
> # dmesg -n 1
> # echo $?
> 0
> # python -m crossbar version
> Traceback (most recent call last):
>   File "usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
>   File "usr/lib/python2.7/runpy.py", line 72, in _run_code
>   File "usr/lib/python2.7/site-packages/crossbar/__main__.py", line 36, in <module>
>   File "usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 479, in load_entry_point
>   File "usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2703, in load_entry_point
>   File "usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2320, in load
>   File "usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2343, in require
>   File "usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 782, in resolve
> pkg_resources.ContextualVersionConflict: (txaio 2.8.2 (/usr/lib/python2.7/site-packages), Requirement.parse('txaio>=18.8.1'), set(['autobahn']))
> # echo $?
> 1
> 
> So it doesn't work due to some dependency issues. Is the timeout
> problem going to appear once those dependency issues are solved ? Or
> should I have already seen the timeout ?

Sorry, I don't know.

Yegor, any idea? Could you bisect this? I already started:
2018.02-rc2-4-gaa77030b8f + patch = timeout
2018.08-425-gc5a33a11be + patch = dependency issue
2018.05-rc3-25-gd937f908f1 + patch = timeout
2018.05-756-g3d34f36806 + patch = (still running:
https://gitlab.com/RicardoMartincoski/buildroot/-/jobs/98611581 )

Regards,
Ricardo


More information about the buildroot mailing list