Skip to content

Conversation

@matlo607
Copy link
Contributor

No description provided.

@matlo607
Copy link
Contributor Author

Hello,

Is the build on Windows meeting some issues ?
The errors are not related at all to my changes and I met exactly the same problem in another pull request (fix-path-test-binaries) on Windows.

24: ======================================================================
24: ERROR: test_ssl_no_name (__main__.ContainerExampleSSLTest)
24: ----------------------------------------------------------------------
24: Traceback (most recent call last):
24:   File "C:/projects/qpid-proton/examples/cpp/example_test.py", line 253, in tearDown
24:     super(ContainerExampleSSLTest, self).tearDown()
24:   File "C:/projects/qpid-proton/examples/cpp/example_test.py", line 108, in tearDown
24:     raise ProcError(b, "broker crash")
24: ProcError: ['broker', '-a', 'APPVYR-WIN:1650'] broker crash, code=-1073740791
24: vvvvvvvvvvvvvvvv
24: broker listening on APPVYR-WIN:1650
24: fixme: dangling listener_maybe_free.  aborting
24: ^^^^^^^^^^^^^^^^
24: 
24: 
24: ----------------------------------------------------------------------
24: Ran 4 tests in 1.391s
24: 
24: FAILED (errors=8)
24/24 Test #24: cpp-example-container-ssl ........***Failed    1.48 sec
88% tests passed, 3 tests failed out of 24
Total Test time (real) =  28.40 sec
The following tests FAILED:
	 10 - cpp-container_test (OTHER_FAULT)
	 23 - cpp-example-container (Failed)
	 24 - cpp-example-container-ssl (Failed)
Errors while running CTest
Command exited with code 8

@matlo607 matlo607 force-pushed the fix-build-gcc49-solaris branch from b411942 to 61e55b7 Compare April 12, 2018 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant