-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PowerPC, tests] "Good rc from connect" asserts fail: rc was -1
#1524
Comments
Have you tried using the REVERSED library compile option? It changes the order of the network data integers which is sometimes needed for Big-endian machines. All tests should fail if this is the issue. |
I did not, but I can try tomorrow. I did not wait until 270 tests complete, since mostly everything was failing (but some passed), however from the log it looks like there is just one failure which breaks tests, while other test cases inside a given test pass. (But I did not dig into the source code, so my impression may be wrong.) |
@icraggs How it should be used? I do not see |
To get a picture of what fails and what passes (I had to interrupt two tests, they seem to freeze indefinitely):
I think |
It's going to be the same problem in each, whatever it is. The only tests that have passed tehre are the ones where the connect is expected to fail, for other reasons. You have started an MQTT broker? If you look at the github workflow for running the CI tests, .github/workflows/build_macos.yml you'll see the setup needed. When I run from the command line, I start the test broker, with the commands in the workflow and then use the cmake-build.sh shell script (from the develop branch). |
Describe the bug
A lot of tests fail on PowerPC (Big-endian) due to the same issue: "good rc from connect" assert fails.
To Reproduce
Run tests on BE powerpc. (I cannot test on Linux/BSD, but the issue might be relevant there as well.)
Expected behavior
All tests should pass.
Log files
Example:
All failures are like this. Looks like everything else passes (but since this assertion sits inside a lot of tests, many tests fail due to that).
** Environment (please complete the following information):**
Additional context
Failure do not appear to be conditional on using
libdispatch
or not. While normally macOS powerpc does not supportlibdispatch
, I have its version locally and can use it with the build (which works fine). Yet, I get identical failures with and withoutlibdispatch
.Build without
libdispatch
is fixed in #1523The text was updated successfully, but these errors were encountered: