Skip to content
Production Build Smoke Test

Orchestrator logs its own requests #1659

Sign in to view logs

Orchestrator logs its own requests

Orchestrator logs its own requests #1659

Triggered via pull request October 6, 2024 18:21
@JonasHelmingJonasHelming
synchronize #14255
GH-14252
Status Failure
Total duration 2m 23s
Artifacts –

production-smoke-test.yml

on: pull_request
Smoke Test for Browser Example Production Build on ubuntu-latest with Node.js 18.x
2m 15s
Smoke Test for Browser Example Production Build on ubuntu-latest with Node.js 18.x
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 1 warning
Smoke Test for Browser Example Production Build on ubuntu-latest with Node.js 18.x: packages/ai-chat/src/common/orchestrator-chat-agent.ts#L103
Cannot find name 'orchestartorRequestID'. Did you mean 'orchestartorRequestId'?
Smoke Test for Browser Example Production Build on ubuntu-latest with Node.js 18.x: packages/ai-chat/src/common/orchestrator-chat-agent.ts#L118
Cannot find name 'OrchestatorRequestIDKey'. Did you mean 'orchestratorRequestID'?
Smoke Test for Browser Example Production Build on ubuntu-latest with Node.js 18.x
Process completed with exit code 2.
Smoke Test for Browser Example Production Build on ubuntu-latest with Node.js 18.x
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-node@1a4442cacd436585916779262731d5b162bc6ec7, actions/setup-python@b64ffcaf5b410884ad320a9cfac8866006a109aa. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/