Skip to content

allow GDAL_jll 301.800 #24

allow GDAL_jll 301.800

allow GDAL_jll 301.800 #24

Workflow file for this run

name: IntegrationTest
on:
push:
branches: [master]
tags: [v*]
pull_request:
jobs:
test:
name: ${{ matrix.package.repo }}/${{ matrix.package.group }}/${{ matrix.julia-version }}
runs-on: ${{ matrix.os }}
env:
GROUP: GDAL
strategy:
fail-fast: false
matrix:
julia-version: [1]
os: [ubuntu-latest]
package:
- {user: yeesian, repo: ArchGDAL.jl, group: GDAL}
- {user: JuliaGeo, repo: GADM.jl, group: GDAL}
- {user: evetion, repo: GeoDataFrames.jl, group: GDAL}
- {user: rafaqz, repo: Rasters.jl, group: GDAL}
steps:
- uses: actions/checkout@v4
- uses: julia-actions/setup-julia@v1
with:
version: ${{ matrix.julia-version }}
arch: x64
- uses: julia-actions/julia-buildpkg@v1
- name: Clone Downstream
uses: actions/checkout@v4
with:
repository: ${{ matrix.package.user }}/${{ matrix.package.repo }}
path: downstream
- name: Load this and run the downstream tests
shell: julia --color=yes --project=downstream {0}
run: |
using Pkg
try
# Force downstream tests to use this PR's version of the package
Pkg.develop(PackageSpec(path=".")) # resolver may fail with main deps
Pkg.update()
Pkg.test(coverage=true) # resolver may fail with test time deps
catch err
err isa Pkg.Resolve.ResolverError || rethrow()
# If we can't resolve that means this is incompatible by SemVer and this is fine
# it means we marked this as a breaking change, so we don't need to worry about
# mistakenly introducing a breaking change, as we have intentionally made one
@info "Not compatible with this release. No problem." exception=err
exit(0) # Exit immediately, as a success
end
- uses: julia-actions/julia-processcoverage@v1
- uses: codecov/codecov-action@v3
with:
file: lcov.info