[ https://issues.apache.org/jira/browse/PROTON-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14330136#comment-14330136 ]
Rafael H. Schloming commented on PROTON-824: -------------------------------------------- PN_TRACE_FRM will log to stderr by default. Python's print statements are going to stdout. You can send the print statements to stderr and see if that helps. > Windows fails testIdleTimeout with assert p.conn.remote_condition > ----------------------------------------------------------------- > > Key: PROTON-824 > URL: https://issues.apache.org/jira/browse/PROTON-824 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c > Affects Versions: 0.9 > Environment: Windows Server 2008 or 2012 > Visual studio 2010, x86 > Reporter: Chuck Rolke > > {noformat} > 1: proton_tests.engine.ServerTest.testIdleTimeout ......................... > fail > 1: Error during test: Traceback (most recent call last): > 1: File "D:/Users/crolke/git/rh-qpid-proton/tests/python/proton-test", > line 355, in run > 1: phase() > 1: File > "D:\Users\crolke\git\rh-qpid-proton\tests\python\proton_tests\engine.py", > line 1919 (or so), in testIdleTimeout > 1: assert p.conn.remote_condition > 1: AssertionError > {noformat} > Playing with Program explicit timeout (trying 10 instead of 3) gets the test > to pass sometimes. It passes sometimes with 3 as well but normally fails. > In debugging this it looks like there as no synchronization between what a > test will show through print statements and what the proton library shows > through PN_TRACE_FRM statements. Are there any hints to lining these up? -- This message was sent by Atlassian JIRA (v6.3.4#6332)