Skip to content
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

Windows Server 2022: "lastMiKTeXException" #503

Closed
DyfanJones opened this issue Jan 17, 2022 · 9 comments
Closed

Windows Server 2022: "lastMiKTeXException" #503

DyfanJones opened this issue Jan 17, 2022 · 9 comments

Comments

@DyfanJones
Copy link

Hi all,

Currently getting the following Note from my rhub window build checks:

checking for detritus in the temp directory ... NOTE
Found the following files/directories:
'lastMiKTeXException'

The linux builds came back ok.

rhub code ran to produce note:

rhub::check_for_cran(env_vars=c(R_COMPILE_AND_INSTALL_PACKAGES = "always", LIBARROW_BINARY="true"))

Any advice would be greatly appreciated.

Linked Github release tickets:
DyfanJones/noctua#180
DyfanJones/RAthena#165

@gaborcsardi
Copy link
Collaborator

Seems like a bug/crash in miktex, so you can ignore this.

@DyfanJones
Copy link
Author

@gaborcsardi thanks for your fast reply, feel free to close this ticket. I will leave it open incase you need to reference it later.

@guyas
Copy link

guyas commented Jan 26, 2022

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?

@gaborcsardi
Copy link
Collaborator

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.

@gaborcsardi
Copy link
Collaborator

Actually, I still see it. :(

@jonthegeek
Copy link

Is there a boilerplate that should be added to cran-comments.md for this, or should we ignore it completely?

@gaborcsardi gaborcsardi reopened this Oct 20, 2022
@gaborcsardi
Copy link
Collaborator

@jonthegeek this is a bug in R-hub, so I would not expect them to be interested in it.

@jonthegeek
Copy link

@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

@gaborcsardi
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants