[jira] [Updated] (PROTON-503) python test failed, but the overall build didnt
[ https://issues.apache.org/jira/browse/PROTON-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-503: -- Fix Version/s: 0.7 > python test failed, but the overall build didnt > --- > > Key: PROTON-503 > URL: https://issues.apache.org/jira/browse/PROTON-503 > Project: Qpid Proton > Issue Type: Test > Environment: Windows 7 x64, running test inside the msysygit 'Git > Bash' shell. >Reporter: Robbie Gemmell >Assignee: Rafael H. Schloming >Priority: Critical > Fix For: 0.7 > > > When working on PROTON-501 and PROTON-502, I ran the tests (using mvn test). > I noticed one of the python tests fail as they ran (see snippets below), and > it was reported as failing when the python tests completed, but not when the > wrapping JUnit tests did, and as result the build itself was erroneously > marked a success. > Test Failure: > == > proton_tests.messenger.NBMessengerTest.testCreditReclaim fail > Error during teardown: Traceback (most recent call last): > File "C:\workspace\proton\tests\python\proton-test", line 352, in run > phase() > File "C:\workspace\proton\tests\python\proton_tests\messenger.py", line > 710, in teardown > assert self.server.stopped > AssertionError > > Test results: > = > Totals: 266 tests, 219 passed, 21 skipped, 25 ignored, 1 failed > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 43.898 sec > Results : > Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 > Build results: > == > [INFO] Reactor Summary: > [INFO] > [INFO] proton-project SUCCESS [1.029s] > [INFO] proton-j .. SUCCESS [6.053s] > [INFO] proton-jms SUCCESS [0.359s] > [INFO] proton-hawtdispatch ... SUCCESS [2.839s] > [INFO] proton-tests .. SUCCESS [45.162s] > [INFO] proton-j-messenger-example SUCCESS [0.281s] > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (PROTON-503) python test failed, but the overall build didnt
[ https://issues.apache.org/jira/browse/PROTON-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-503: -- Summary: python test failed, but the overall build didnt (was: NBMessengerTest.testCreditReclaim failed, but the overall build didnt) > python test failed, but the overall build didnt > --- > > Key: PROTON-503 > URL: https://issues.apache.org/jira/browse/PROTON-503 > Project: Qpid Proton > Issue Type: Test > Environment: Windows 7 x64, running test inside the msysygit 'Git > Bash' shell. >Reporter: Robbie Gemmell >Priority: Critical > > When working on PROTON-501 and PROTON-502, I ran the tests (using mvn test). > I noticed one of the python tests fail as they ran (see snippets below), and > it was reported as failing when the python tests completed, but not when the > wrapping JUnit tests did, and as result the build itself was erroneously > marked a success. > Test Failure: > == > proton_tests.messenger.NBMessengerTest.testCreditReclaim fail > Error during teardown: Traceback (most recent call last): > File "C:\workspace\proton\tests\python\proton-test", line 352, in run > phase() > File "C:\workspace\proton\tests\python\proton_tests\messenger.py", line > 710, in teardown > assert self.server.stopped > AssertionError > > Test results: > = > Totals: 266 tests, 219 passed, 21 skipped, 25 ignored, 1 failed > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 43.898 sec > Results : > Tests run: 9, Failures: 0, Errors: 0, Skipped: 0 > Build results: > == > [INFO] Reactor Summary: > [INFO] > [INFO] proton-project SUCCESS [1.029s] > [INFO] proton-j .. SUCCESS [6.053s] > [INFO] proton-jms SUCCESS [0.359s] > [INFO] proton-hawtdispatch ... SUCCESS [2.839s] > [INFO] proton-tests .. SUCCESS [45.162s] > [INFO] proton-j-messenger-example SUCCESS [0.281s] > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
