Skip to content

Update GitHub Action workflows#51

Open
fingolfin wants to merge 2 commits intoJuliaDocs:masterfrom
fingolfin:mh/ci
Open

Update GitHub Action workflows#51
fingolfin wants to merge 2 commits intoJuliaDocs:masterfrom
fingolfin:mh/ci

Conversation

@fingolfin
Copy link
Contributor

No description provided.

@fingolfin
Copy link
Contributor Author

Turns out tests are broken in different ways

First, Project.toml claims that Julia 1.3 is the minimal supported version, but it fails to resolve compatible versions of Franklin and Logging (?)

With newer Julia versions (1.6, 1.10) it produces lots of node / npm related warnings:

  Activating environment at `/tmp/jl_cEnK8M/foo/Project.toml`
→ Initial full pass...

→ evaluating code [ex] in (index.md)                                            
npm WARN saveError ENOENT: no such file or directory, open '/tmp/jl_cEnK8M/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN notsup Unsupported engine for glob@11.0.3: wanted: {"node":"20 || >=22"} (current: {"node":"12.22.1","npm":"6.14.12"})
npm WARN notsup Not compatible with your version of node/npm: glob@11.0.3
npm WARN notsup Unsupported engine for commander@12.1.0: wanted: {"node":">=18"} (current: {"node":"12.22.1","npm":"6.14.12"})
npm WARN notsup Not compatible with your version of node/npm: commander@12.1.0
npm WARN notsup Unsupported engine for jackspeak@4.1.1: wanted: {"node":"20 || >=22"} (current: {"node":"12.22.1","npm":"6.14.12"})
npm WARN notsup Not compatible with your version of node/npm: jackspeak@4.1.1
npm WARN notsup Unsupported engine for minimatch@10.0.3: wanted: {"node":"20 || >=22"} (current: {"node":"12.22.1","npm":"6.14.12"})
npm WARN notsup Not compatible with your version of node/npm: minimatch@10.0.3
npm WARN notsup Unsupported engine for path-scurry@2.0.0: wanted: {"node":"20 || >=22"} (current: {"node":"12.22.1","npm":"6.14.12"})
npm WARN notsup Not compatible with your version of node/npm: path-scurry@2.0.0
npm WARN notsup Unsupported engine for minipass@7.1.2: wanted: {"node":">=16 || 14 >=14.17"} (current: {"node":"12.22.1","npm":"6.14.12"})
npm WARN notsup Not compatible with your version of node/npm: minipass@7.1.2
npm WARN notsup Unsupported engine for foreground-child@3.3.1: wanted: {"node":">=14"} (current: {"node":"12.22.1","npm":"6.14.12"})
npm WARN notsup Not compatible with your version of node/npm: foreground-child@3.3.1
npm WARN notsup Unsupported engine for signal-exit@4.1.0: wanted: {"node":">=14"} (current: {"node":"12.22.1","npm":"6.14.12"})
npm WARN notsup Not compatible with your version of node/npm: signal-exit@4.1.0
npm WARN notsup Unsupported engine for @isaacs/brace-expansion@5.0.0: wanted: {"node":"20 || >=22"} (current: {"node":"12.22.1","npm":"6.14.12"})
npm WARN notsup Not compatible with your version of node/npm: @isaacs/brace-expansion@5.0.0
npm WARN notsup Unsupported engine for @isaacs/balanced-match@4.0.1: wanted: {"node":"20 || >=22"} (current: {"node":"12.22.1","npm":"6.14.12"})
npm WARN notsup Not compatible with your version of node/npm: @isaacs/balanced-match@4.0.1
npm WARN notsup Unsupported engine for lru-cache@11.2.2: wanted: {"node":"20 || >=22"} (current: {"node":"12.22.1","npm":"6.14.12"})
npm WARN notsup Not compatible with your version of node/npm: lru-cache@11.2.2
npm WARN enoent ENOENT: no such file or directory, open '/tmp/jl_cEnK8M/package.json'
npm WARN jl_cEnK8M No description
npm WARN jl_cEnK8M No repository field.
npm WARN jl_cEnK8M No README data
npm WARN jl_cEnK8M No license field.

→ Use Pkg.activate() to go back to your main environment.                       + purgecss@7.0.2
+ highlight.js@11.11.1
added 50 packages from 64 contributors and audited 50 packages in 2.67s

15 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

  Activating environment at `/tmp/jl_cEnK8M/foo/Project.toml`

→ Use Pkg.activate() to go back to your main environment.                       

→ Full pass (no pre-rendering)     [done   2.1s]                               
/tmp/jl_cEnK8M/node_modules/commander/lib/command.js:396
eOrNameAndArgs = enableOrNameAndArgs ?? 'help [command]';
                                               ^

SyntaxError: Unexpected token '?'
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/tmp/jl_cEnK8M/node_modules/commander/index.js:2:21)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
optimize: Error During Test at /home/runner/work/PkgPage.jl/PkgPage.jl/test/instantiate.jl:35
  Got exception outside of a @test
...

With Julia 1.12 and nightly, we get this added into the mix:

  Activating project at `/tmp/jl_jWsx3e/foo`
WARNING: Detected access to binding `Main.Utils_2` in a world prior to its definition world.
  Julia 1.12 has introduced more strict world age semantics for global bindings.
  !!! This code may malfunction under Revise.
  !!! This code will error in future versions of Julia.
Hint: Add an appropriate `invokelatest` around the access to this binding.
To make this warning an error, and hence obtain a stack trace, use `julia --depwarn=error`.
┌ Franklin Warning: in <index.md>
│ Encountered an issue processing 'index.md' in /tmp/jl_jWsx3e/foo.
│ Verify, then re-start the Franklin server.
│ The error is displayed below:
│ Franklin.LxObjError("Command or environment 'section' was used before it was\ndefined.")
└

@tlienart
Copy link
Collaborator

Thanks for trying to fix this looks like it's not an easy one

Not sure when/if I'll have the time to investigate but thanks so much for giving it a shot :)

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

Successfully merging this pull request may close these issues.

2 participants