We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
System under test is an aarch64 box (Packet type 2A) running this gcc:
gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4)
I applied #50 , and all of the demangler unit tests passed. Now I am faced with this, the signalhandler_unittest failing:
hhvm@ed-2a-sjc-dcos:/home/src/github.com/google/glog$ make check make logging_striplog_test_sh demangle_unittest_sh signalhandler_unittest_sh make[1]: Entering directory '/home/src/github.com/google/glog' ./src/logging_striplog_test.sh In DBG mode; not checking strings PASS ./demangle_unittest # force to create lt-demangle_unittest Passed 3 tests PASS ./src/demangle_unittest.sh PASS ./signalhandler_unittest # force to create lt-signalhandler_unittest OK ./src/signalhandler_unittest.sh 'SIGFPE' should appear in the output Makefile:2065: recipe for target 'signalhandler_unittest_sh' failed make[1]: *** [signalhandler_unittest_sh] Error 1 make[1]: Leaving directory '/home/src/github.com/google/glog' Makefile:1908: recipe for target 'check-am' failed make: *** [check-am] Error 2
In looking at this perhaps this is relate to #177 (fails on ppc64le) in some sense.
The text was updated successfully, but these errors were encountered:
so, how do you solve this problem?
Sorry, something went wrong.
@Amazingren I have not solved this problem myself, and the ticket is still open.
No branches or pull requests
System under test is an aarch64 box (Packet type 2A) running this gcc:
I applied #50 , and all of the demangler unit tests passed. Now I am faced with this, the signalhandler_unittest failing:
In looking at this perhaps this is relate to #177 (fails on ppc64le) in some sense.
The text was updated successfully, but these errors were encountered: