In our automated tests, we encountered a "segmentation fault" when running fetch:

We encountered this again, and again in a <a href="https://circleci.com/gh/gruntwork-i

One-Time Segmentation Fault about fetch HOT 1 CLOSED

gruntwork-io commented on June 7, 2024

One-Time Segmentation Fault

from fetch.

Comments (1)

josh-padnick commented on June 7, 2024

We encountered this again, and again in a CircleCI run.

gruntwork-install --module-name "gruntwork-module-circleci-helpers" --repo "https://github.com/gruntwork-io/module-ci" --tag "v0.0.1"
Installing gruntwork-module-circleci-helpers...
Downloading module gruntwork-module-circleci-helpers from https://github.com/gruntwork-io/module-ci
/usr/local/bin/gruntwork-install: line 70: 14031 Segmentation fault      fetch --repo="$repo" --tag="$tag" --branch="$branch" --github-oauth-token="$github_token" "/modules/$module_name" "$download_path/$module_name" > /dev/null

gruntwork-install --module-name "gruntwork-module-circleci-helpers" --repo "https://github.com/gruntwork-io/module-ci" --tag "v0.0.1" returned exit code 139

Action failed: gruntwork-install --module-name "gruntwork-module-circleci-helpers" --repo "https://github.com/gruntwork-io/module-ci" --tag "v0.0.1"

I suspect we have periodic unexpected responses from GitHub and that fetch isn't handling them correctly.

from fetch.

Recommend Projects