Skip to content

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

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

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

Triggered via pull request April 22, 2026 10:00
Status Failure
Total duration 4h 39m 30s
Artifacts 1

test-shared.yml

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

Annotations

6 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:91945) 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:91945) ExperimentalWarning: zlib/iter is an experimental feature and might change at any time (node:98541) 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:98548) 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:98555) 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:98563) 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:98570) 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:98577) 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:98584) 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:98591) 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:98598) 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:98605) 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:98612) 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:98619) 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:98626) 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:98633) 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:98640) 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:98647) 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:98654) 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:98661) 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:98669) SecurityWarnin
x86_64-darwin: with shared libraries
Process completed with exit code 2.
x86_64-darwin: with shared libraries: test/benchmark/test-benchmark-fs.js#L0
--- stderr --- (node:18106) 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:18106) ExperimentalWarning: zlib/iter is an experimental feature and might change at any time (node:24640) 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:24652) 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:24659) 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:24671) 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:24683) 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:24690) 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:24705) 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:24718) 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:24731) 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:24738) 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:24750) 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:24763) 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:24775) 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:24782) 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:24798) 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:24811) 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:24823) 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:24835) 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:24847) SecurityWarnin

Artifacts

Produced during runtime
Name Size Digest
tarballs
50.3 MB
sha256:495a4dcf239d221a54e4c30e00b934822657032a3a5f556dba7b7f6156f5e0bf