[ 
https://issues.apache.org/jira/browse/DISPATCH-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16970290#comment-16970290
 ] 

ASF GitHub Bot commented on DISPATCH-1471:
------------------------------------------

ChugR commented on issue #613: DISPATCH-1471: print strings that fail assert
URL: https://github.com/apache/qpid-dispatch/pull/613#issuecomment-551870030
 
 
   Fixed at commit 3b7b8a1
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> [test] When string comparison asserts fail the strings are not printed
> ----------------------------------------------------------------------
>
>                 Key: DISPATCH-1471
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1471
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 1.9.0
>            Reporter: Charles E. Rolke
>            Assignee: Charles E. Rolke
>            Priority: Major
>
> Tests fail in CI environments far away. Accessing a system identical to the 
> CI system for development work is a problem. Here is a CI failure:
> {quote}File 
> "/opt/interconnect-src/tests/system_tests_topology_disposition.py", 
>          line 459, in test_04_scraper_tool
>  self.assertEqual ( None, error )
>  AssertionError: None != 'Process 7713 error: exit code 126, expec[311 
> chars]<<<<<'
> {quote}
> The test is trying to print the error message. Instead the message is 
> truncated and the hint *[311 chars]* is shown. It would be *really* useful to 
> show those 311 chars.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to