You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use PkgBenchmark with one of the private packages we've developed at my company. We have a private registry. The registry and packages are stored on a self-hosted GitLab instance.
I have a script that is more or less doing the following:
using PkgBenchmark
pkg_root =abspath(@__DIR__, "..") # this script lives in the benchmark subdirectory, so I'm pointing up one levelfunctionbenchmark_config(; kw...)
BenchmarkConfig(juliacmd=`julia -O3`,
env=Dict("JULIA_NUM_THREADS"=>1);
kw...)
end
target =benchmarkpkg(pkg_root, benchmark_config())
baseline =benchmarkpkg(pkg_root, benchmark_config(id="8d33882")) # this is line 26 in the stack trace below
I have a hard-coded id there just to test things out. Eventually, I'll use git merge-base to figure out the correct id.
I can run this locally on my Mac just fine. When I try to call this using GitLab CI, with a runner on a Linux machine, I get the error below.
That "EG" registry is our private registry. Line 26 of run_ci.jl is the second call to benchmarkpkg above. It's like it is trying to operate on the registry's repo instead of my package's repo.
I'm using Julia 1.6.1 on both systems, and I'm using v0.2.11 of PkgBenchmark.
I set JULIA_DEPOT_PATH to force the runner to start with a fresh depot. I've looked at the environment variables that GitLab CI is setting, but nothing jumped out at me.
I can try to reduce this down to a simpler demonstration of the problem, but I thought I'd post what I have so far, in case something jumps out to someone.
The text was updated successfully, but these errors were encountered:
I was able to work around the issue by using LibGit2 to check out the appropriate version of the code myself.
using PkgBenchmark
import LibGit2
pkg_root =abspath(@__DIR__, "..") # this script lives in the benchmark subdirectory, so I'm pointing up one levelfunctionbenchmark_config(; kw...)
BenchmarkConfig(juliacmd=`julia -O3`,
env=Dict("JULIA_NUM_THREADS"=>1);
kw...)
end
target =benchmarkpkg(pkg_root, benchmark_config())
repo = LibGit2.GitRepo(pkg_root)
LibGit2.checkout!(repo, baseline_hash)
baseline =benchmarkpkg(pkg_root, benchmark_config())
LibGit2.checkout!(repo, target_hash)
This makes me think even more that PkgBenchmark is passing the wrong repo to a LibGit2 call somewhere...
I'm trying to use PkgBenchmark with one of the private packages we've developed at my company. We have a private registry. The registry and packages are stored on a self-hosted GitLab instance.
I have a script that is more or less doing the following:
I have a hard-coded
id
there just to test things out. Eventually, I'll usegit merge-base
to figure out the correctid
.I can run this locally on my Mac just fine. When I try to call this using GitLab CI, with a runner on a Linux machine, I get the error below.
That "EG" registry is our private registry. Line 26 of
run_ci.jl
is the second call tobenchmarkpkg
above. It's like it is trying to operate on the registry's repo instead of my package's repo.I'm using Julia 1.6.1 on both systems, and I'm using v0.2.11 of PkgBenchmark.
I set
JULIA_DEPOT_PATH
to force the runner to start with a fresh depot. I've looked at the environment variables that GitLab CI is setting, but nothing jumped out at me.I can try to reduce this down to a simpler demonstration of the problem, but I thought I'd post what I have so far, in case something jumps out to someone.
The text was updated successfully, but these errors were encountered: