-
Notifications
You must be signed in to change notification settings - Fork 52
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
PREPERROR: Debian Linux, R-devel, GCC ASAN/UBSAN #576
Comments
What is your question? |
How to fix this error? |
I am sorry, you will have to be more specific? What is the error you see in the log? The preperror itself might be nothing. Did you see an installation or other error? If yes, what is the error message? |
This the error when I ran this code: results <- rhub::check_for_cran(). |
You need to look at the log file to see if there is an error. I took a quick look and it seems to me that there is no error, but you might see this false positive: #445. |
This is my error |
another error |
Those are not errors with your R package. You need to look at the output of |
this is the results after run rhub::list_my_checks(email = "[email protected]") |
@gaborcsardi I'm getting a somewhat similar problem. I tested my package on several platforms and no errors were found but on this platform, i.e. Debian Linux, R-devel, GCC ASAN/UBSAN I'm getting a PREPERROR but then it says "status: success". In my case the error seems to be related to some cookies. Here is the log: https://builder.r-hub.io/status/GPvecchia_0.1.6.tar.gz-b07654500c6e412293ef1fd3d46987a5 I would be happy to ignore this problem but I'm submitting the package to CRAN and if it's an error on the rhub's side, may I cite this issue as explanation? Thanks for your work on this great tool, Rhub team! |
This issue is about the previous R-hub system, it does not apply to the new system, so I am closing it now. Please see https://r-hub.github.io/rhub/ for the new system, R-hub v2. |
HTML:https://builder.r-hub.io/status/HDNRA_1.0.0.tar.gz-0cc20e94585040308e9220555270a1e2
From the above link, the status is success, but I still this problem.
The text was updated successfully, but these errors were encountered: