Execution Fails due to Missing range.match #322
Description
We are using the github-action-benchmark since some time for our benchmarking of the overhead of tracing tools: https://github.com/kieker-monitoring/moobench Unfortunately, since yesterday, uploading the results fails (https://github.com/kieker-monitoring/moobench/actions/runs/17452452482/job/49559739982) with the following log:
Run benchmark-action/github-action-benchmark@v1
with:
name: Kieker-java
tool: customSmallerIsBetter
output-file-path: output.json
fail-on-alert: true
github-token: ***
auto-push: true
gh-pages-branch: gh-pages
benchmark-data-dir-path: dev/bench
skip-fetch-gh-pages: false
comment-always: false
summary-always: false
save-data-file: true
comment-on-alert: false
alert-threshold: 200%
env:
R_LIBS_USER: /home/runner/work/_temp/Library
TZ: UTC
_R_CHECK_SYSTEM_CLOCK_: FALSE
NOT_CRAN: true
JAVA_HOME: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/21.0.8-9/x64
JAVA_HOME_21_X64: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/21.0.8-9/x64
/usr/bin/git -c user.name=github-action-benchmark -c user.email=github@users.noreply.github.com -c http.https://github.com/.extraheader= fetch ***github.com/kieker-monitoring/moobench.git gh-pages:gh-pages
From https://github.com/kieker-monitoring/moobench
* [new branch] gh-pages -> gh-pages
/usr/bin/git -c user.name=github-action-benchmark -c user.email=github@users.noreply.github.com -c http.https://github.com/.extraheader= switch gh-pages
Switched to branch 'gh-pages'
/usr/bin/git -c user.name=github-action-benchmark -c user.email=github@users.noreply.github.com -c http.https://github.com/.extraheader= pull ***github.com/kieker-monitoring/moobench.git gh-pages
From https://github.com/kieker-monitoring/moobench
* branch gh-pages -> FETCH_HEAD
Already up to date.
/usr/bin/git -c user.name=github-action-benchmark -c user.email=github@users.noreply.github.com -c http.https://github.com/.extraheader= checkout -
Switched to branch 'main'
Your branch is up to date with 'origin/main'.
Error: range.match is not a function
Is there a known problem here / a workaround to fix this? I would guess that the some JS update on the github actions environment caused the issue, but if this is true, I'd guess that it should not only happen for our environment.