Compare commits

...

7 Commits

Author SHA1 Message Date
Eric Hanson
1aec431e02 Restrict annotation functionality to versions of Julia it works on (#79)
* Restrict annotation functionality to versions of Julia it works on

see #76

* Update README.md
2023-04-02 23:23:43 +02:00
Sascha Mann
4867b265f3 Add warning about annotate (#77) 2023-03-22 23:17:43 +01:00
Fredrik Ekre
3378215696 Export the JULIA_PKG_SERVER_REGISTRY_PREFERENCE variable for subsequent steps. (#75) 2023-03-13 18:32:24 +01:00
Fredrik Ekre
ba451bf755 Use eager registry flavor instead of git clone. (#74) 2023-03-13 12:21:51 +01:00
Sascha Mann
fa1e6fac94 Print executed command in debug mode (#72) 2023-01-08 20:50:11 +00:00
Sascha Mann
8d20cd78f8 Support prefixes with args (#71)
Supersedes #48

Co-authored-by: Ian Butterworth <i.r.butterworth@gmail.com>
2023-01-08 21:39:24 +01:00
Simon Christ
c80d3075f7 prevent double tests (#60) 2022-12-19 22:47:16 -05:00
3 changed files with 27 additions and 70 deletions

View File

@@ -11,7 +11,12 @@ An example workflow that uses this action might look like this:
```yaml
name: Run tests
on: [push, pull_request]
on:
push:
branches:
- master
- main
pull_request:
jobs:
test:
@@ -33,13 +38,15 @@ jobs:
arch: ${{ matrix.julia-arch }}
- uses: julia-actions/julia-buildpkg@v1
- uses: julia-actions/julia-runtest@v1
with:
annotate: true
# with:
# annotate: true
```
You can add this workflow to your repository by placing it in a file called `test.yml` in the folder `.github/workflows/`. [More info here](https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions).
Here, setting `annotate: true` causes GitHub "annotations" to appear when reviewing the PR, pointing to failing tests, if any.
This functionality is only enabled on Julia 1.8 (even if `annotate` is set to `true`), since currently it does not work on other Julia versions (see #76).
By default, `annotate` is set to false, but that may change in future releases of this action.
### Prefixing the Julia command
@@ -73,3 +80,13 @@ If you only want to add this prefix on certain builds, you can [include addition
```
This will add the prefix `xvfb-run` to all builds where the `os` is `ubuntu-latest`.
### Registry flavor preference
This actions defines (and exports for subsequent steps of the workflow) the
environmental variable `JULIA_PKG_SERVER_REGISTRY_PREFERENCE=eager` unless it
is already set. If you want another registry flavor (i.e. `conservative`) this
should be defined in the `env:` section of the relevant workflow or step. See
[Registry flavors](https://pkgdocs.julialang.org/dev/registries/#Registry-flavors)
for more information.

View File

@@ -36,25 +36,13 @@ inputs:
runs:
using: 'composite'
steps:
# Occasionally, there are rather large delays (> a few hours)
# between the time a package is registered in General and
# propagated to pkg.julialang.org. We can avoid this by manually
# cloning ~/.julia/registries/General/ in Julia 1.5 and later.
# See:
# * https://github.com/JuliaLang/Pkg.jl/issues/2011
# * https://github.com/JuliaRegistries/General/issues/16777
# * https://github.com/JuliaPackaging/PkgServer.jl/issues/60
- run: julia --color=yes "$GITHUB_ACTION_PATH"/add_general_registry.jl
- name: Set and export registry flavor preference
run: echo "JULIA_PKG_SERVER_REGISTRY_PREFERENCE=${JULIA_PKG_SERVER_REGISTRY_PREFERENCE:-eager}" >> ${GITHUB_ENV}
shell: bash
env:
# We set `JULIA_PKG_SERVER` only for this step to enforce
# `Pkg.Registry.add` to use Git. This way, Pkg.jl can send
# the request metadata to pkg.julialang.org when installing
# packages via `Pkg.test`.
JULIA_PKG_SERVER: ""
- name: Install dependencies in their own (shared) environment
run: |
if VERSION > v"1.8pre"
# Functionality only currently works on a narrow range of Julia versions... see #76
if v"1.8pre" < VERSION < v"1.9.0-beta3"
using Pkg
Pkg.activate("tests-logger-env"; shared=true)
Pkg.add(Pkg.PackageSpec(name="GitHubActions", version="0.1"))
@@ -66,10 +54,11 @@ runs:
julia_cmd=( julia --color=yes --depwarn=${{ inputs.depwarn }} --inline=${{ inputs.inline }} --project=${{ inputs.project }} -e 'include(joinpath(ENV["GITHUB_ACTION_PATH"], "test_harness.jl"))' )
# Add the prefix in front of the command if there is one
prefix="${{ inputs.prefix }}"
[[ -n $prefix ]] && julia_cmd=( "$prefix" "${julia_cmd[@]}" )
prefix=( ${{ inputs.prefix }} )
[[ -n ${prefix[*]} ]] && julia_cmd=( "${prefix[@]}" "${julia_cmd[@]}" )
# Run the Julia command
echo "::debug::Executing Julia: ${julia_cmd[*]}"
"${julia_cmd[@]}"
shell: bash
env:

View File

@@ -1,49 +0,0 @@
using Pkg
function general_registry_location()
general_registry_dir = joinpath(DEPOT_PATH[1], "registries", "General")
registry_toml_file = joinpath(general_registry_dir, "Registry.toml")
return general_registry_dir, registry_toml_file
end
function general_registry_exists()
general_registry_dir, registry_toml_file = general_registry_location()
if !isdir(general_registry_dir)
return false
elseif !isfile(registry_toml_file)
return false
else
return true
end
end
function add_general_registry()
@info("Attempting to clone the General registry")
general_registry_dir, registry_toml_file = general_registry_location()
rm(general_registry_dir; force = true, recursive = true)
Pkg.Registry.add("General")
isfile(registry_toml_file) || throw(ErrorException("the Registry.toml file does not exist"))
return nothing
end
function main(; n = 10, max_delay = 120)
VERSION >= v"1.5-" || return
if general_registry_exists()
@info("The General registry already exists locally")
return
end
delays = ExponentialBackOff(; n = n, max_delay = max_delay)
try
retry(add_general_registry; delays = delays)()
@info("Successfully added the General registry")
catch ex
msg = "I was unable to add the General registry. However, the build will continue."
@error(msg, exception=(ex,catch_backtrace()))
end
return
end
main()