Skip to content
Test

feat: run GitLab E2E for labeled fork pull requests #564

Sign in to view logs

feat: run GitLab E2E for labeled fork pull requests

feat: run GitLab E2E for labeled fork pull requests #564

Triggered via pull request September 12, 2026 09:46
@fengmk2fengmk2
opened #149
gitlab-e2e-fork-label
Status Success
Total duration 1m 3s
Artifacts –

test.yml

on: pull_request
test-auto-node-version
9s
test-auto-node-version
test-cache-npm
11s
test-cache-npm
test-cache-yarn
14s
test-cache-yarn
test-registry-url
6s
test-registry-url
test-alpine-container
19s
test-alpine-container
test-sfw-alpine
15s
test-sfw-alpine
test-sfw-with-socketdev-action
11s
test-sfw-with-socketdev-action
build
22s
build
Matrix: test-azure-runtime
Matrix: test-cache-bun
Matrix: test-cache-pnpm
Matrix: test-default-version
Matrix: test-node-manager-off
Matrix: test-node-version
Matrix: test-preview-build
Matrix: test-sfw-blocks-malicious
Matrix: test-sfw
Matrix: test-vp-exec
Matrix: test-vp-install-and-exec
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
test-sfw-alpine
Failed to save: "/bin/tar" failed with error: The process '/bin/tar' failed with exit code 1
test-sfw-blocks-malicious (windows-latest)
sfw reported vp as not found even though it is on PATH. This is a known sfw flake on Windows: a cold PowerShell start exceeds sfw's 10s command-resolution timeout and the timeout is misreported as not-found. Warming the PowerShell command cache and retrying once.