Actions
Bug #268
closedTest device/fenv failed to run
Status:
Closed
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
03/13/2013
Due date:
% Done:
100%
Estimated time:
CPU Architecture:
x86
Host OS:
Linux, Mac OS X, Windows
Toolchain:
clang-3.1, clang-3.2, gcc-4.4.3, gcc-4.6, gcc-4.7
Android version:
CrystaX NDK Version:
Description
NB This is x86 specific error.
Sample output:
COMMAND: /opt/android/android-sdk-linux/platform-tools/adb -s emulator-5558 shell chmod 0755 /data/local/tmp/ndk-tests/test_fenv_c¶
Running device test [x86]: fenv (test_fenv_c)
/opt/android/android-sdk-linux/platform-tools/adb -s "emulator-5558" shell "cd /data/local/tmp/ndk-tests && LD_LIBRARY_PATH=/data/local/tmp/ndk-tests ./test_fenv_c"
ERROR jni/test_fenv.c:116 feclearexcept_fetestexcept: (raised & FE_DIVBYZERO) != 0
ERROR jni/test_fenv.c:121 feclearexcept_fetestexcept: (raised & FE_DIVBYZERO) != 0
test-return-code:1
---> TEST FAILED!!
Updated by Alexander Z. about 11 years ago
- Description updated (diff)
- CPU Architecture x86 added
- Host OS Linux added
- Toolchain clang-3.1, clang-3.2, gcc-4.4.3, gcc-4.6, gcc-4.7 added
Updated by Alexander Z. about 11 years ago
- Priority changed from Urgent to Low
- Target version deleted (
r8-crystax-1)
Google's r8e shows the same behavior.
The problem was that r8e's run-test.sh script incorrectly skipped device/fenv build for x86 abi.
Updated by Dmitry M. over 9 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
Already fixed
Actions