-
Notifications
You must be signed in to change notification settings - Fork 23
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
devtools::test
failed
#178
Comments
Yeah, this has been a bit of a problem lately. the test is supposed to check behaviour with NAs, but there seems to be inconsistencies between platforms. At least this is the only way I see it failing on some but not others. As I don't have an M1 I can't debug this. |
Please let me know if I can help. I can fork and test on my machine. Also I requested a PR #177 so that you can have github action to check the package for you on osx. A script to install (without brew) is also included in that PR. This might be helpful when brew arch is different from R (for example, ARM brew with x86 R installed, users can compile x86 HDF5 by themselves without having two brews in the same system) |
Thanks for this - I will merge it. And yes, please debug it, that would be great. Am thankful for help. Personally I have not used this package in years, so am doing this in my spare time as much as I can. |
Here's the issue hdf5r/tests/testthat/test-64bit_support.R Line 88 in 5c9074f
All other tests passed. |
More information: Bit information: > bit64::as.bitstring(dbl_vec_int64_na[18])
[1] "0111111111111111111111111111111111111111111111111111111111111111"
> bit64::as.bitstring(bit64::NA_integer64_)
[1] "1000000000000000000000000000000000000000000000000000000000000000" |
The problem is here: Line 278 in 5c9074f
This is so weird... Wrote a simple C to test it: SEXP print_bit(SEXP obj){
uint64_t tmp = *REAL0(obj);
printf("%llu ", tmp);
return(R_NilValue);
} > bit64::as.integer64(dbl_vec[18])
integer64
[1] 9223372036854775807
> print_bit(dbl_vec[18])
9223372036854775808 NULL |
It seems
This little difference cause I've posted this issue on Your package seems fine. Small changes on the test might be desired. I'll create a PR soon. |
Asked help from
|
Great - thanks for following up on this. If this is truly undefined, then
yes I think bit64 needs to handle this as per your pull request. Over the
weekend I have some time and will review and merge all this. Thanks for all
your work!
…On Thu, Aug 12, 2021 at 1:47 PM Dipterix Wang ***@***.***> wrote:
Asked help from r-devel, their reply seems confirming my guess:
https://stat.ethz.ch/pipermail/r-devel/2021-August/080986.html
bit64 is handling an undefined conversion, and hdf5r is doing right.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#178 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASGMYU7BUPCTEOLM7Z5Z2TT4OYD7ANCNFSM5B6XFTEQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
* added github actions to check the repo * added build ignore for gh action checks; set system path to include h5cc * minor fix for non-osx * updated to HDF5 1.12.1 * See #178 and r-lib/bit64#19
I tried
devtools::test()
on github fork. It showed an error:The text was updated successfully, but these errors were encountered: