[stdout] Docker app's state test === RUN TestAppStatus apps: '[eclient]' state: 'RUNNING' secs: 1200 time: 2024-05-17T07:41:09.112450304Z out: appName eclient state changed to UNKNOWN time: 2024-05-17T07:41:10.95039436Z out: appName eclient state changed to INITIAL app_test.go:171: ASSERTION FAILED (2024-05-17T08:01:09.113425997Z): expected apps [eclient] in RUNNING state app_test.go:173: actual eclient: INITIAL app_test.go:175: history of states for eclient: app_test.go:177: state: no info from controller received in: 2024-05-17T07:41:09.108989326Z app_test.go:177: state: UNKNOWN received in: 2024-05-17T07:41:09.112448782Z app_test.go:177: state: INITIAL received in: 2024-05-17T07:41:10.950390663Z --- app eclient logs --- ------ testContext.go:285: WaitForProcWithErrorCallback terminated by timeout 20m0s --- FAIL: TestAppStatus (1201.01s) FAIL [exit status 1] FAIL: ../eclient/testdata/metadata.txt:17: command failure

Process completed with exit code 1.

[stdout] Docker app's state test === RUN TestAppStatus apps: '[dhcp-server]' state: 'RUNNING' secs: 600 time: 2024-05-17T08:06:38.741797285Z out: appName dhcp-server state changed to UNKNOWN time: 2024-05-17T08:06:39.07492032Z out: appName dhcp-server state changed to INITIAL app_test.go:171: ASSERTION FAILED (2024-05-17T08:16:38.742774808Z): expected apps [dhcp-server] in RUNNING state app_test.go:173: actual dhcp-server: INITIAL app_test.go:175: history of states for dhcp-server: app_test.go:177: state: no info from controller received in: 2024-05-17T08:06:38.736390699Z app_test.go:177: state: UNKNOWN received in: 2024-05-17T08:06:38.741794008Z app_test.go:177: state: INITIAL received in: 2024-05-17T08:06:39.074916464Z --- app dhcp-server logs --- ------ testContext.go:285: WaitForProcWithErrorCallback terminated by timeout 10m0s --- FAIL: TestAppStatus (601.01s) FAIL [exit status 1] FAIL: ../network/testdata/switch_net_vlans.txt:45: command failure

Process completed with exit code 1.

[stdout] Docker app's state test === RUN TestAppStatus apps: '[local-manager]' state: 'RUNNING' secs: 600 time: 2024-05-17T08:06:56.473054674Z out: appName local-manager state changed to UNKNOWN time: 2024-05-17T08:06:59.364005698Z out: appName local-manager state changed to INITIAL time: 2024-05-17T08:06:59.364057847Z out: appName local-manager state changed to UNKNOWN app_test.go:171: ASSERTION FAILED (2024-05-17T08:16:56.473980487Z): expected apps [local-manager] in RUNNING state app_test.go:173: actual local-manager: UNKNOWN app_test.go:175: history of states for local-manager: app_test.go:177: state: no info from controller received in: 2024-05-17T08:06:56.470886641Z app_test.go:177: state: UNKNOWN received in: 2024-05-17T08:06:56.473053522Z app_test.go:177: state: INITIAL received in: 2024-05-17T08:06:59.364002602Z app_test.go:177: state: UNKNOWN received in: 2024-05-17T08:06:59.364057466Z --- app local-manager logs --- ------ testContext.go:285: WaitForProcWithErrorCallback terminated by timeout 10m0s --- FAIL: TestAppStatus (601.00s) FAIL [exit status 1] FAIL: ../eclient/testdata/profile.txt:28: command failure

Process completed with exit code 1.

The self-hosted runner: buildjet.com_fca1f11a-62af-44d4-8ccc-bbb2149aa933 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

The self-hosted runner: buildjet.com_3148987c-e8cc-4856-b2e5-643c359b1475 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

[stdout] Docker app deployment Test === RUN TestDockerStart docker_test.go:189: time: 2024-05-17T08:07:49.492679901Z out: Add app to list config changed, to see config run 'eden controller edge-node get-config' docker_test.go:195: time: 2024-05-17T08:07:50.500056676Z out: Add processing of app messages docker_test.go:199: time: 2024-05-17T08:07:50.500089357Z out: Add processing of app running messages docker_test.go:203: time: 2024-05-17T08:07:50.500099837Z out: Add function to obtain EVE IP docker_test.go:207: time: 2024-05-17T08:07:50.500108072Z out: Add trying to access app via http testProc.go:84: time: 2024-05-17T08:07:58.062910625Z out: projects.ProcTimerFunc done with return: external ip is: 127.0.0.1 testProc.go:84: time: 2024-05-17T08:08:37.263805009Z out: projects.ProcInfoFunc done with return: app found with name t1 testContext.go:302: WaitForProc terminated by timeout 20m0s testContext.go:285: WaitForProcWithErrorCallback terminated by timeout 20m0s --- FAIL: TestDockerStart (1202.44s) FAIL [stderr] time="2024-05-17T08:07:58Z" level=info msg="time: 2024-05-17T08:07:58.062910625Z out: projects.ProcTimerFunc done with return: external ip is: 127.0.0.1" time="2024-05-17T08:08:37Z" level=info msg="time: 2024-05-17T08:08:37.263805009Z out: projects.ProcInfoFunc done with return: app found with name t1" [exit status 1] FAIL: ../docker/testdata/2dockers_test.txt:13: command failure

Process completed with exit code 1.

[stdout] Log/Info/Metric Test === RUN TestInfo lim_test.go:273: time: 2024-05-17T08:06:36.008880557Z out: Wait for info of d82b540e-e617-491a-8edb-fe04c497414d number=1 timewait=30m0s testContext.go:302: WaitForProc terminated by timeout 30m0s testContext.go:285: WaitForProcWithErrorCallback terminated by timeout 30m0s --- FAIL: TestInfo (1800.00s) FAIL [exit status 1] FAIL: ../update_eve_image/testdata/update_eve_image_http.txt:46: command failure

Process completed with exit code 1.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-go@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.