Update CHANGELOG.md #382
Annotations
21 errors
2022.3.45f1 (StandaloneLinux64, with unity loc, no unitask)
Process completed with exit code 1.
|
2022.3.45f1 (StandaloneLinux64, with unity loc, no unitask)
Process completed with exit code 1.
|
2022.3.45f1 (StandaloneLinux64, with unity loc, no unitask)
Process completed with exit code 1.
|
2022.3.45f1 (StandaloneLinux64, with unity loc, no unitask)
Process completed with exit code 1.
|
2022.3.45f1 (StandaloneLinux64, no unity loc, with unitask)
Process completed with exit code 1.
|
2022.3.45f1 (StandaloneLinux64, no unity loc, with unitask)
Process completed with exit code 1.
|
2022.3.45f1 (StandaloneLinux64, no unity loc, with unitask)
Process completed with exit code 1.
|
2022.3.45f1 (StandaloneLinux64, no unity loc, with unitask)
Process completed with exit code 1.
|
2022.3.45f1 (StandaloneLinux64, no unity loc, no unitask)
Process completed with exit code 1.
|
2022.3.45f1 (StandaloneLinux64, no unity loc, no unitask)
Process completed with exit code 1.
|
2022.3.45f1 (StandaloneLinux64, no unity loc, no unitask)
Process completed with exit code 1.
|
2022.3.45f1 (StandaloneLinux64, no unity loc, no unitask)
Process completed with exit code 1.
|
2023.2.12f1 (StandaloneLinux64, no unity loc, no unitask)
The self-hosted runner: linux-1 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.
|
2023.2.12f1 (StandaloneLinux64, with unity loc, no unitask)
The self-hosted runner: linux-2 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.
|
2022.3.45f1 (StandaloneLinux64, with unity loc, with unitask)
The self-hosted runner: linux-0 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.
|
6000.0.24f1 (StandaloneLinux64, no unity loc, no unitask)
Canceling since a higher priority waiting request for 'Run Tests 🧪-6000.0.24f1-false-false' exists
|
2023.2.12f1 (StandaloneLinux64, no unity loc, with unitask)
Canceling since a higher priority waiting request for 'Run Tests 🧪-2023.2.12f1-false-true' exists
|
6000.0.24f1 (StandaloneLinux64, with unity loc, no unitask)
Canceling since a higher priority waiting request for 'Run Tests 🧪-6000.0.24f1-true-false' exists
|
2023.2.12f1 (StandaloneLinux64, with unity loc, with unitask)
Canceling since a higher priority waiting request for 'Run Tests 🧪-2023.2.12f1-true-true' exists
|
6000.0.24f1 (StandaloneLinux64, with unity loc, with unitask)
Canceling since a higher priority waiting request for 'Run Tests 🧪-6000.0.24f1-true-true' exists
|
6000.0.24f1 (StandaloneLinux64, no unity loc, with unitask)
Canceling since a higher priority waiting request for 'Run Tests 🧪-6000.0.24f1-false-true' exists
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
Test results (edit + play, 2022.3.45f1 StandaloneLinux64 no-unity-loc no-unitask)
|
1.94 KB |
|
Test results (edit + play, 2022.3.45f1 StandaloneLinux64 no-unity-loc with-unitask)
|
1.92 KB |
|
Test results (edit + play, 2022.3.45f1 StandaloneLinux64 with-unity-loc no-unitask)
|
1.92 KB |
|