curl: command not found when job runs in container
#4
Comments
|
👋 @mcuelenaere: Thanks for reporting this! This is really bizarre, and it's definitely not the experience I want people to have. 😬 I haven't been able to reproduce this just yet, but I'm looking into it today. Thanks for including the job environment info:
I've never had any issues with I'll investigate this further, and I'll follow up with you today. |
|
This error is indeed very puzzling, I haven't rerun the workflow yet (doing that now). Maybe this was just a fluke? This is the complete workflow job (certain parts have been censored): test:
name: Test
runs-on: ubuntu-latest
container:
image: ubuntu:latest
services:
redis:
image: redis:6
ports:
- 6379/tcp
mysql:
image: mysql:5.7
ports:
- 3306/tcp
env:
MYSQL_ROOT_PASSWORD: ***
MYSQL_DATABASE: ***
vault:
image: vault:1.5.0
ports:
- 8200/tcp
env:
VAULT_DEV_ROOT_TOKEN_ID: ***
options: "--cap-add IPC_LOCK"
steps:
- name: Checkout
uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
node-version: '16'
scope: ***
registry-url: 'https://npm.pkg.github.com/'
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
- name: Cache NPM
uses: actions/cache@v3
with:
path: ~/.npm
key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-node-
- name: Install dependencies
run: npm i
- name: Linting
run: npm run lint
- name: Validate TypeScript
run: npm run check:typescript
- name: Tests
run: npm run test:ci
env:
NODE_ENV: ci
TS_NODE_TRANSPILE_ONLY: "true"
TZ: UTC
- name: Upload test results to BuildPulse for flaky test detection
if: '!cancelled()'
uses: Workshop64/buildpulse-action@main
with:
account: ***
repository: ***
path: ./test-results.xml
key: ${{ secrets.BUILDPULSE_ACCESS_KEY_ID }}
secret: ${{ secrets.BUILDPULSE_SECRET_ACCESS_KEY }} |
Thanks so much for that, @mcuelenaere. After seeing the workflow definition, I was able to reproduce the issue. For some reason, this entry in the workflow job triggers the problem: container:
image: ubuntu:latestI pushed up an example repository in a branch to reproduce the issue. Without the Then, I added the I don't yet know why the Thanks again for sharing the workflow definition to help reproduce this problem! |
|
@mcuelenaere: I suspect I'll need to open an issue in the @actions org to try to figure out why we're seeing this problem. To unblock you in the meantime, I found a solution that you could use temporarily while I investigate this further: This patch resolves the problem: fa34615...efc1ff1 To do so, it does two things:
With those two changes in place, the BuildPulse action completes successfully even with the Is this something that you'd be willing to try? |
jasonrudolph
changed the title
curl: command not found when job runs in container
|
@jasonrudolph that seems to work, yes! |
@mcuelenaere: Great! I'm glad that got things working for you. I'm sorry for the clunky workaround. Thanks for your flexibility. I've asked about this problem in community/community#13718. Hopefully we'll hear back from the @actions team or the community to find out if this is a bug with composite actions or if there's a different approach that I need to use in this action. |
Uploading the test results fails with
curl: command not found. Unsure why such a basic utility would be missing. This was our first experience setting up Buildpulse.Full logs:
Job environment:
Relevant excerpt from workflow:
The text was updated successfully, but these errors were encountered: