Closed DyfanJones closed 4 months ago
Seems like a bug/crash in miktex, so you can ignore this.
@gaborcsardi thanks for your fast reply, feel free to close this ticket. I will leave it open incase you need to reference it later.
I have tried again today, from a different computer. Not only that the note persists, the CRAN does not build the package for windows and yesterday I also got some weird PREPERROR.
Any ideas why?
For the record, this is because we set TMPDIR
, and MikTeX will pick it up to write out some error report there, here-ish: https://github.com/MiKTeX/miktex/blob/ab8ebca7c70fe8c9a1392dfb2393a0a7683e14cc/Libraries/MiKTeX/Core/Exceptions.cpp#L163
Now I also set MIKTEX_ENV_EXCEPTION_PATH
to c:\temp
on the builders, so that should take care of this NOTE.
Actually, I still see it. :(
Is there a boilerplate that should be added to cran-comments.md
for this, or should we ignore it completely?
@jonthegeek this is a bug in R-hub, so I would not expect them to be interested in it.
@gaborcsardi thanks! I thought that was the case but wasn't sure, and was led back to this issue by someone else's cran-comment.md mentioning it
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.
Hi all,
Currently getting the following
Note
from my rhub window build checks:The linux builds came back ok.
rhub
code ran to produce note:Any advice would be greatly appreciated.
Linked Github release tickets: https://github.com/DyfanJones/noctua/issues/180 https://github.com/DyfanJones/RAthena/issues/165