Skip to content

permission: add --allow-env flag for environment variable access control #5859

permission: add --allow-env flag for environment variable access control

permission: add --allow-env flag for environment variable access control #5859

Triggered via pull request April 24, 2026 05:36
Status Failure
Total duration 3h 54m 30s
Artifacts 1

test-shared.yml

on: pull_request
Build slim tarball
4m 1s
Build slim tarball
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

5 errors
aarch64-linux: with shared libraries
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
x86_64-linux: with shared libraries
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
aarch64-darwin: with shared libraries
Process completed with exit code 2.
aarch64-darwin: with shared libraries: test/benchmark/test-benchmark-fs.js#L0
--- stderr --- (node:23491) ExperimentalWarning: stream/iter is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the warning was created) (node:23491) ExperimentalWarning: zlib/iter is an experimental feature and might change at any time (node:29980) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:29987) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:29994) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30001) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30008) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30015) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30022) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30029) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30037) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30044) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30051) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30058) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30065) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30072) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30079) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30086) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30093) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30100) SecurityWarning: The flag --allow-child-process must be used with extreme caution. It could invalidate the permission model. (Use `node --trace-warnings ...` to show where the warning was created) (node:30107) SecurityWarnin
x86_64-darwin: with shared libraries
Process completed with exit code 2.

Artifacts

Produced during runtime
Name Size Digest
tarballs
50.3 MB
sha256:5ccfdaa7d15ff2bbeb4a8d8d905c1f98fccf16c87f8f41637279813d53571ac0