effects-interpreter
checks.x86_64-linux.effects-interpreter
· build #1615
· raw
1--- registry secretsMap per trigger2--- build_finished registry mapping and defaults3--- buildFinished maps to an unguarded event with literal argv and only its own secrets4--- buildFinished defaults grant no secrets and append no revision5--- buildFinished missing declared secret fails before the program runs6error: CLOUDFLARE_API_TOKEN missing from $HERCULES_CI_SECRETS_JSON7--- buildFinished missing forge token fails before the program runs8error: GITHUB_FORGE_TOKEN missing from $HERCULES_CI_SECRETS_JSON9--- main execs the program with --rev and its secrets10CI-RUN-CONTEXT: branch=main is_main=true11--- main on a non-main token is skipped12EFFECT-GUARD: skipping outside a push to main (event=push ref=refs/heads/gitea-mq/batch/7)13--- main on a pull_request token is skipped14EFFECT-GUARD: skipping outside a push to main (event=pull_request ref=)15--- main without the id-token endpoint is refused16EFFECT-GUARD: NIXBOT_ID_TOKEN_REQUEST_URL and NIXBOT_ID_TOKEN_REQUEST_TOKEN are required; declare idTokenAudiences on the effect17--- main whose id-token fetch fails is refused18EFFECT-GUARD: failed to obtain an id token from nixbot19--- missing secret fails before the program runs20CI-RUN-CONTEXT: branch=main is_main=true21error: GITHUB_TOKEN missing from $HERCULES_CI_SECRETS_JSON22--- null secret fails before the program runs23CI-RUN-CONTEXT: branch=main is_main=true24error: GITHUB_TOKEN missing from $HERCULES_CI_SECRETS_JSON25--- pullRequest runs unguarded, without --rev, with the forge token26--- missing forge token fails before the program runs27error: GITHUB_FORGE_TOKEN missing from $HERCULES_CI_SECRETS_JSON28--- pullRequestClosed runs unguarded, without --rev, without the forge token29--- missing secret fails a pullRequestClosed run before the program runs30error: CLOUDFLARE_API_TOKEN missing from $HERCULES_CI_SECRETS_JSON31--- pullRequest never receives the main trigger's secrets32--- main never receives the pullRequest trigger's secrets or forge token33CI-RUN-CONTEXT: branch=main is_main=true34--- registry: release-packages pullRequest runs the plan with the forge token and never GITHUB_TOKEN35--- registry: release-packages pullRequest without the forge token fails before the program runs36error: GITHUB_FORGE_TOKEN missing from $HERCULES_CI_SECRETS_JSON37--- registry: release-packages main receives GITHUB_TOKEN and not the forge token38CI-RUN-CONTEXT: branch=main is_main=true39--- registry: docs pullRequestClosed receives Cloudflare and not the forge token40--- registry: browser-evidence buildFinished uploads with the R2 secrets and nixbot's API token, without --rev41--- registry: browser-evidence buildFinished without an R2 secret fails before the program runs42error: R2_EVIDENCE_ACCESS_KEY_ID missing from $HERCULES_CI_SECRETS_JSON43--- registry: browser-evidence pullRequest uploads with the R2 secrets and nixbot's API token, without --rev44--- registry: browser-evidence pullRequest without an R2 secret fails before the program runs45error: R2_EVIDENCE_ACCESS_KEY_ID missing from $HERCULES_CI_SECRETS_JSON46--- registry: browser-evidence main appends --rev and receives the R2 secrets and nixbot's API token47CI-RUN-CONTEXT: branch=main is_main=true