Hello,

I locally added the print you suggested and it returned:
qdrouterd: Cannot find Python library path

So it's a configuration problem on our side.

Thanks,
Olivier

-----Original Message-----
From: Robbie Gemmell <robbie.gemm...@gmail.com>
Sent: mercredi 12 février 2020 16:58
To: users@qpid.apache.org
Subject: Re: [Dispatch Router] unit test failure on master

FWIW, it seems to be passing on 2.7 in CI:
https://travis-ci.org/apache/qpid-dispatch/builds/649151581

On Wed, 12 Feb 2020 at 15:29, Chuck Rolke <cro...@redhat.com> wrote:
>
> Hi Oliver,
>
> That test should work with python27. Please raise a jira for this.
>
> As it stands the test does not leave a paper trail of why the test failed.
> Useful information would be produced by patching the test and
> including the output generated by
>   'ctest -VV -R system_tests_bad_configuration'
>
> Thanks,
> Chuck
>
> diff --git a/tests/system_tests_bad_configuration.py
> b/tests/system_tests_bad_configuration.py
> index 32a24fcf..499af9eb 100644
> --- a/tests/system_tests_bad_configuration.py
> +++ b/tests/system_tests_bad_configuration.py
> @@ -194,6 +194,7 @@ class RouterTestIdFailCtrlChar(TestCase):
>              stdin=PIPE, stdout=PIPE, stderr=STDOUT, expect=Process.EXIT_FAIL,
>              universal_newlines=True)
>          out = p.communicate(timeout=5)[0]
> +        print("ctrl-char out:", out)
>          try:
>              p.teardown()
>          except Exception as e:
>
>
>
> ----- Original Message -----
> > From: "VERMEULEN Olivier" <olivier.vermeu...@murex.com>
> > To: users@qpid.apache.org
> > Sent: Wednesday, February 12, 2020 2:58:42 AM
> > Subject: [Dispatch Router] unit test failure on master
> >
> > Hello,
> >
> > We are monitoring the dispath-router master branch on our own CI.
> > It has been consistently failing for the path 2 weeks with the error below.
> > Those 2 tests were introduced by DISPATCH-1553.
> > Is it also failing on your side or is it a configuration issue on ours?
> >
> > Thanks,
> > Olivier
> >
> >
> > test 49
> >       Start 49: system_tests_bad_configuration
> >
> > 49: Test command: /opt/rh/python27/root/usr/bin/python
> > "/data/jenkins-slave/home/workspace/_messaging-utilities_master-RTRHCLWXOYN5UQPWAUKGQXTBZ7TFTF7MSRUNGRRMSPII4BHC6HTA/dispatch-router/build-dir/qpid-dispatch/tests/run.py"
> > "-m" "unittest" "-v" "system_tests_bad_configuration"
> > 49: Test timeout computed to be: 600
> > 49: test_qdmanage_query
> > (system_tests_bad_configuration.RouterTestBadConfiguration) ... ok
> > 49: test_unresolvable_host_caught
> > (system_tests_bad_configuration.RouterTestBadConfiguration) ... ok
> > 49:
> > 49: Router QDR.A debug dump file:
> > 49: alloc.c: Items of type 'qd_timer_t' remain allocated at
> > shutdown: 1
> > 49: alloc.c: Items of type 'qd_connector_t' remain allocated at
> > shutdown: 1
> > 49: test_verify_reject_id_with_ctrl_char
> > (system_tests_bad_configuration.RouterTestIdFailCtrlChar) ... FAIL
> > 49: test_verify_reject_id_with_whitespace
> > (system_tests_bad_configuration.RouterTestIdFailWhiteSpace) ... FAIL
> > 49:
> > 49:
> > ====================================================================
> > ==
> > 49: FAIL: test_verify_reject_id_with_ctrl_char
> > (system_tests_bad_configuration.RouterTestIdFailCtrlChar)
> > 49:
> > --------------------------------------------------------------------
> > --
> > 49: Traceback (most recent call last):
> > 49:   File
> > "/data/jenkins-slave/home/workspace/_messaging-utilities_master-RTRH
> > CLWXOYN5UQPWAUKGQXTBZ7TFTF7MSRUNGRRMSPII4BHC6HTA/dispatch-router/qpi
> > d-dispatch-master/tests/system_tests_bad_configuration.py",
> > line 201, in test_verify_reject_id_with_ctrl_char
> > 49:     self.assertTrue("AttributeError" in out)
> > 49: AssertionError: False is not true
> > 49:
> > 49:
> > ====================================================================
> > ==
> > 49: FAIL: test_verify_reject_id_with_whitespace
> > (system_tests_bad_configuration.RouterTestIdFailWhiteSpace)
> > 49:
> > --------------------------------------------------------------------
> > --
> > 49: Traceback (most recent call last):
> > 49:   File
> > "/data/jenkins-slave/home/workspace/_messaging-utilities_master-RTRH
> > CLWXOYN5UQPWAUKGQXTBZ7TFTF7MSRUNGRRMSPII4BHC6HTA/dispatch-router/qpi
> > d-dispatch-master/tests/system_tests_bad_configuration.py",
> > line 239, in test_verify_reject_id_with_whitespace
> > 49:     self.assertTrue("AttributeError" in out)
> > 49: AssertionError: False is not true
> > 49:
> > 49:
> > --------------------------------------------------------------------
> > --
> > 49: Ran 4 tests in 1.344s
> > 49:
> > 49: FAILED (failures=2)
> > 49/62 Test #49: system_tests_bad_configuration
> > ....................***Failed
> > 1.42 sec
> >
> > *******************************
> > This e-mail contains information for the intended recipient only. It
> > may contain proprietary material or confidential information. If you
> > are not the intended recipient you are not authorized to distribute,
> > copy or use this e-mail or any attachment to it. Murex cannot
> > guarantee that it is virus free and accepts no responsibility for any loss 
> > or damage arising from its use.
> > If you have received this e-mail in error please notify immediately
> > the sender and delete the original email received, any attachments
> > and all copies from your system.
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For
> additional commands, e-mail: users-h...@qpid.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional 
commands, e-mail: users-h...@qpid.apache.org

*******************************
This e-mail contains information for the intended recipient only. It may 
contain proprietary material or confidential information. If you are not the 
intended recipient you are not authorized to distribute, copy or use this 
e-mail or any attachment to it. Murex cannot guarantee that it is virus free 
and accepts no responsibility for any loss or damage arising from its use. If 
you have received this e-mail in error please notify immediately the sender and 
delete the original email received, any attachments and all copies from your 
system.

Reply via email to