-
Notifications
You must be signed in to change notification settings - Fork 192
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
Failed test when running ffi_bit64.lua in v2.1-20200102 #90
Comments
I've tried to add |
@amdei I copied your shell commands and ran them on a relatively clean Debian buster x86_64 system on my side and could not reproduce the test failure you are seeing: $ /opt/luajit21/bin/luajit test/ffi/ffi_bit64.lua; echo $?
0 Will you run that I also tried your build flags and the same git tag ( BTW, you need to set I guess there may be something strange in your system environment. Not sure. You'll need to dig into that assertion failure with tools like gdb on your side. Too little information is currently known. |
BTW, i'm also using the default gcc in Debian 10: $ gcc --version
gcc (Debian 8.3.0-6) 8.3.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
|
@agentzh Thanks a lot for a prompt reply! Seems you're right - something was wrong with my system... Tried with other two different fresh and clean Debian 9&10 VMs. At the same time, when I try to specify
it fails 7 other tests. Tried to specify
with much better result - all test has passed! So, one need to specify |
BTW, after adding of
all test has passed on machine, where they failed in the first place. So, complete "working for me" example is the following:
|
Debian 10 Buster x64
On clean system:
As a result, I've got:
test/ffi/ffi_bit64.lua:18 is:
What's wrong with my setup?
How can I overcome this issue?
Actual result of this snippet:
is
0ULL
The text was updated successfully, but these errors were encountered: