-
Notifications
You must be signed in to change notification settings - Fork 27
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
Test issue for non-Intel architectures #78
Comments
Ping? |
I wonder if the silence about this bug is connected to the advise to switch to gbm3. Unfortunately there are several packages in Debian (and thus CRAN) that depend on this version of gbm. I wonder whether the issue is visible also on CRAN test builds on non-Intel architectures. |
Silence mostly due to day jobs. Can you try the following:
|
Hi Greg,
Am Thu, Apr 25, 2024 at 06:58:14AM -0700 schrieb Greg Ridgeway:
Silence mostly due to day jobs.
Fine. Will be true for me as well in the next couple of weeks.
I was just elected as Debian Project Leader and all my packaging
duties are left behind a bit. I try to do my best in debugging
but it might last some time.
l
Can you try the following:
1. Install from github if you can't from CRAN, remotes::install_github("gbm-developers/gbm")
2. Run the test script inst/tinytest/test_least_squares.R
3. Let us know what the value of
best.iter
mean(data2$Y - f.predict)
sd(data2$Y - f.predict)
I put this somewhere on my todo list.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
after upgrading the Debian package from version 2.1.8.1 to 2.1.9 the CI test we are running on different architectures failed for all non-Intel architectures which you can see in the debci check matrix. When you have a look into one of the test logs - for instance for arm64 you can find the problem is here:
It might be that relaxing the test condition could help passing this test again but I have to less knowledge about the internals of this package.
Kind regards, Andreas.
The text was updated successfully, but these errors were encountered: