test: install and use latexmk

[muzimuzhi]

for https://github.com/teatimeguest/setup-texlive-action/issues/252

[muzimuzhi]

On Windows, latexmk -lualatex [-jobname=...] "simple.tex" hangs in both bash and pwsh shells.
https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsshell

[muzimuzhi]

On Windows, latexmk -lualatex [-jobname=...] "simple.tex" hangs in both bash and pwsh shells. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsshell

After hanging for ~8 min (link), it succeeded, see https://github.com/muzimuzhi/hello-github-actions/actions/runs/4948656780/jobs/8855447360.

Thu, 11 May 2023 18:03:00 GMT Transcript written on simple-windows-luatex.log.
Thu, 11 May 2023 18:10:52 GMT Latexmk: Getting log file 'simple-windows-luatex.log'

A second run is as fast as expected, see https://github.com/muzimuzhi/hello-github-actions/actions/runs/4951590205/jobs/8856767579. Related to luatex cache? GitHub Actions status?

• https://www.githubstatus.com/incidents/pr3498h3qkfy
• https://www.githubstatus.com/incidents/nf7s6933tnn8

[muzimuzhi]

Let's trigger the workflow again, with setup-texlive-action cache for Win deleted.

[muzimuzhi]

Another pair of run attempts:

• attempt 1, slow https://github.com/muzimuzhi/hello-github-actions/actions/runs/4953183451/jobs/8860379892
• attempt 2, quick https://github.com/muzimuzhi/hello-github-actions/actions/runs/4953183451/jobs/8860896881

Differences:

• In slow run, latexmk found a rerun is needed because file $(kpsewhich --var-value TEXMFVAR)/luatex-cache/generic/fonts/otl/lmroman10-regular.lua is created or modified.
• In quick run and all other quick cases in slow run, no rerun happened.

Thu, 11 May 2023 22:41:40 GMT Output written on simple-windows-luatex.pdf (1 page, 2993 bytes).
Thu, 11 May 2023 22:41:40 GMT Transcript written on simple-windows-luatex.log.
Thu, 11 May 2023 22:48:36 GMT Latexmk: Getting log file 'simple-windows-luatex.log'
Thu, 11 May 2023 22:48:36 GMT Latexmk: Examining 'simple-windows-luatex.fls'
Thu, 11 May 2023 22:48:36 GMT Latexmk: ============== Inequiv cwd_fls cwd 'D:/a/hello-github-actions/hello-github-actions/latex-examples' '/d/a/hello-github-actions/hello-github-actions/latex-examples'
Thu, 11 May 2023 22:48:36 GMT Latexmk: Examining 'simple-windows-luatex.log'
Thu, 11 May 2023 22:48:36 GMT Latexmk: Log file says output to 'simple-windows-luatex.pdf'
Thu, 11 May 2023 22:48:36 GMT Latexmk: applying rule 'lualatex'...
Thu, 11 May 2023 22:48:36 GMT Rule 'lualatex':  Reasons for rerun
Thu, 11 May 2023 22:48:36 GMT Changed files or newly in use/created:
Thu, 11 May 2023 22:48:36 GMT   D:/a/_temp/setup-texlive/2023/texmf-var/luatex-cache/generic/fonts/otl/lmroman10-regular.lua

Also from the downloaded artifact, in simple-windows-luatex.fdb_latexmk created by rerun, only **/lmroman10-regular.luc, the compiled **/lmroman10-regular.lua, is listed.

I guess somehow latexmk triggered sth similar to luaotfload --update. Does latexmk support executing user commands just before reruns?

---

The TeX Live Guide says

3.4.4 "System font configuration for XeTeX and LuaTeX"
https://tug.org/texlive/doc/texlive-en/texlive-en.html#x1-330003.4.4

The luaotfload font name index may need to be rebuilt for new fonts; this is triggered automatically when trying to load a font which isn’t known yet.

[muzimuzhi]

From https://github.com/muzimuzhi/hello-github-actions/actions/runs/4954707699, it seems that setup-texlive-action didn't generate LuaTeX font cache on Windows only, or the cache was generated in a wrong directory.

Two evidences:

• On Windows, cache files $(kpsewhich --var-value TEXMFSYSVAR)/luatex-cache/generic/fonts/otl/lmroman10-regular.{lua,luc} not found after setup-texlive-action and before running latexmk -lualatex ...
  https://github.com/muzimuzhi/hello-github-actions/actions/runs/4954707699/jobs/8863453263#step:5:1
• On Windows, log of first lualatex run contains
  https://github.com/muzimuzhi/hello-github-actions/actions/runs/4954707699/jobs/8863453263#step:6:51

  luaotfload | db : Font names database not found, generating new one.
  luaotfload | db : This can take several minutes; please be patient.)
  

Remaining

• Next step: test if running luaotfload --update ahead solves the problem, and how long it takes.
  8 min for generating font cache in a rather slim texlive 2023 is incredibly inefficient.
  • doc for luaotfload cli: https://github.com/latex3/luaotfload/blob/main/doc/luaotfload-tool.rst
• Why Windows?
• Why latexmk?
  Simple lualatex simple.tex runs fast. Caused by -recorder?
• Any chances that on Windows the font caches were created in another directory?

cc: @teatimeguest

[muzimuzhi]

Wait a minute. I only deleted GitHub Actions cache for win, so the observation could be totally wrong.

[muzimuzhi]

I think this paragraph in manpage for luaotfload explains quite something (https://github.com/latex3/luaotfload/blob/main/doc/luaotfload-tool.rst#files, also texdoc luaotfload, Appx. "Manual of luaotfload-tool"):

FILES
The font name database is usually located in the directory texmf-var/luatex-cache/generic/names/ ($TEXMFCACHE as set in texmf.cnf) of your TeX Live distribution as a zlib-compressed file luaotfload-names.lua.gz. The experimental lookup cache will be created as luaotfload-lookup-cache.lua in the same directory. These Lua tables are not used directly by Luaotfload, though. Instead, they are compiled to Lua bytecode which is written to corresponding files with the extension .luc in the same directory. When modifying the files by hand keep in mind that only if the bytecode files are missing will Luaotfload use the plain version instead. Both kinds of files are safe to delete, at the cost of regenerating them with the next run of LuaTeX.

So the second run of LuaTeX matters.

I feel close to file an issue to setup-texlive-action asking for pre-generating luatex font cache by running luaotfload-tool --update.

[muzimuzhi]

I think this paragraph in manpage for luaotfload explains quite something [...]

Nope. latexmk -lualatex ... reruns lualatex on all OS and executing luaotfload-tool --update on Win is rather fast.
https://github.com/muzimuzhi/hello-github-actions/actions/runs/4955112169