Build failures reported from the launcher #987

Open
opened 2026-11-16 00:50:26 +00:00 by gab9281 · 2 comments
Member

Build failures that players send from the launcher land here, as #81 does for crashes.

When a build stops, the launcher's problem page offers Send to the team (LongshotLauncher#128). Nothing is sent until the player presses it, and Show what is sent shows the report first. Longshot-api's /telemetry/build relay then:

  • posts one comment per failure (same error, numbers and paths aside), with the first report: launcher and game versions, channel, what the build was, the system, PC (memory, threads, GPUs), the build's settings, why it stopped and the last error line, and the build log's last 200 lines (home folder shown as ~; no game files, no saves);
  • adds later reports of the same failure to that comment's count, with the versions, channels, systems and launchers it was seen on;
  • posts at most 10 new failures an hour.

Counts and trends are on Grafana's Longshot build failures dashboard. Please keep discussion of a specific failure in its own issue, and link the comment from it.

Build failures that players send from the launcher land here, as #81 does for crashes. When a build stops, the launcher's problem page offers **Send to the team** (LongshotLauncher#128). Nothing is sent until the player presses it, and **Show what is sent** shows the report first. Longshot-api's `/telemetry/build` relay then: - posts **one comment per failure** (same error, numbers and paths aside), with the first report: launcher and game versions, channel, what the build was, the system, PC (memory, threads, GPUs), the build's settings, why it stopped and the last error line, and the build log's last 200 lines (home folder shown as `~`; no game files, no saves); - adds later reports of the same failure to that comment's count, with the versions, channels, systems and launchers it was seen on; - posts at most 10 new failures an hour. Counts and trends are on Grafana's **Longshot build failures** dashboard. Please keep discussion of a specific failure in its own issue, and link the comment from it.
Collaborator

Build failed: error: API test failure, safe to delete

e90ea0275d03 · seen 2 times · first 2026-11-16 00:53 UTC · last 2026-11-16 00:53 UTC

Seen on
Versions 0.0.0-api-test (2)
Channels API test (2)
Operating systems Arch Linux (API test) (2)
Launchers 0.0.0-api-test (2)

First report

Launcher 0.0.0-api-test
Version 0.0.0-api-test
Channel API test
Build Install
Operating system Arch Linux (API test)
PC API test PC
Settings API test settings
Why it stopped API test of /telemetry/build (Claude), safe to delete
Last error error: API test failure, safe to delete
The build's log, its last 2 lines
live test of data-services.magicbean.dev/telemetry/build
safe to delete
### Build failed: `error: API test failure, safe to delete` `e90ea0275d03` · **seen 2 times** · first 2026-11-16 00:53 UTC · last 2026-11-16 00:53 UTC | Seen on | | |---|---| | Versions | `0.0.0-api-test` (2) | | Channels | `API test` (2) | | Operating systems | `Arch Linux (API test)` (2) | | Launchers | `0.0.0-api-test` (2) | <!-- first-report --> **First report** | | | |---|---| | Launcher | `0.0.0-api-test` | | Version | `0.0.0-api-test` | | Channel | `API test` | | Build | `Install` | | Operating system | `Arch Linux (API test)` | | PC | `API test PC` | | Settings | `API test settings` | | Why it stopped | `API test of /telemetry/build (Claude), safe to delete` | | Last error | `error: API test failure, safe to delete` | <details><summary>The build's log, its last 2 lines</summary> ``` live test of data-services.magicbean.dev/telemetry/build safe to delete ``` </details> <!-- longshot-build:eyJzaWciOiJlOTBlYTAyNzVkMDMiLCJ3aHkiOiJBUEkgdGVzdCBvZiAvdGVsZW1ldHJ5L2J1aWxkIChDbGF1ZGUpLCBzYWZlIHRvIGRlbGV0ZSIsImVycm9yIjoiZXJyb3I6IEFQSSB0ZXN0IGZhaWx1cmUsIHNhZmUgdG8gZGVsZXRlIiwiY291bnQiOjIsImZpcnN0IjoxNzk0NzkwNDA1LCJsYXN0IjoxNzk0NzkwNDA3LCJ2ZXJzaW9ucyI6eyIwLjAuMC1hcGktdGVzdCI6Mn0sImNoYW5uZWxzIjp7IkFQSSB0ZXN0IjoyfSwib3MiOnsiQXJjaCBMaW51eCAoQVBJIHRlc3QpIjoyfSwibGF1bmNoZXJzIjp7IjAuMC4wLWFwaS10ZXN0IjoyfX0=.97269beef301f6b8fadae4ae74533578 -->
Collaborator

Build failed: telemetry test: make_game.py was stopped by a signal (SIGTERM) from outside the launcher.

3072e3f6aa03 · seen 2 times · first 2026-11-16 06:32 UTC · last 2026-11-16 06:32 UTC

Seen on
Versions 0.0.0-api-test (2)
Channels Nightly (2)
Operating systems CachyOS (Linux 7.3.4-1-cachyos), X64 (2)
Launchers 0.0.0-api-test (2)

First report

Launcher 0.0.0-api-test
Version 0.0.0-api-test
Channel Nightly
Build first build
How it ended terminated
Operating system CachyOS (Linux 7.3.4-1-cachyos), X64
CPU AMD Ryzen 7 6800H with Radeon Graphics
PC 15 GB, 16 threads, NVIDIA and AMD GPU
Settings memory automatic, workers automatic
Stages read 100% 201 s, lift 100% 340 s, compile 37% 401 s
Why it stopped telemetry test: make_game.py was stopped by a signal (SIGTERM) from outside the launcher.
Last error not known
The build's log, its last 2 lines
@@stage compile Compiling
telemetry test, not a real failure
### Build failed: `telemetry test: make_game.py was stopped by a signal (SIGTERM) from outside the launcher.` `3072e3f6aa03` · **seen 2 times** · first 2026-11-16 06:32 UTC · last 2026-11-16 06:32 UTC | Seen on | | |---|---| | Versions | `0.0.0-api-test` (2) | | Channels | `Nightly` (2) | | Operating systems | `CachyOS (Linux 7.3.4-1-cachyos), X64` (2) | | Launchers | `0.0.0-api-test` (2) | <!-- first-report --> **First report** | | | |---|---| | Launcher | `0.0.0-api-test` | | Version | `0.0.0-api-test` | | Channel | `Nightly` | | Build | `first build` | | How it ended | `terminated` | | Operating system | `CachyOS (Linux 7.3.4-1-cachyos), X64` | | CPU | `AMD Ryzen 7 6800H with Radeon Graphics` | | PC | `15 GB, 16 threads, NVIDIA and AMD GPU` | | Settings | `memory automatic, workers automatic` | | Stages | `read 100% 201 s, lift 100% 340 s, compile 37% 401 s` | | Why it stopped | `telemetry test: make_game.py was stopped by a signal (SIGTERM) from outside the launcher.` | | Last error | `not known` | <details><summary>The build's log, its last 2 lines</summary> ``` @@stage compile Compiling telemetry test, not a real failure ``` </details> <!-- longshot-build:eyJzaWciOiIzMDcyZTNmNmFhMDMiLCJ3aHkiOiJ0ZWxlbWV0cnkgdGVzdDogbWFrZV9nYW1lLnB5IHdhcyBzdG9wcGVkIGJ5IGEgc2lnbmFsIChTSUdURVJNKSBmcm9tIG91dHNpZGUgdGhlIGxhdW5jaGVyLiIsImVycm9yIjoiIiwiY291bnQiOjIsImZpcnN0IjoxNzk0ODEwNzQwLCJsYXN0IjoxNzk0ODEwNzYyLCJ2ZXJzaW9ucyI6eyIwLjAuMC1hcGktdGVzdCI6Mn0sImNoYW5uZWxzIjp7Ik5pZ2h0bHkiOjJ9LCJvcyI6eyJDYWNoeU9TIChMaW51eCA3LjMuNC0xLWNhY2h5b3MpLCBYNjQiOjJ9LCJsYXVuY2hlcnMiOnsiMC4wLjAtYXBpLXRlc3QiOjJ9fQ==.c46b132c58c5430f39072bce8408e903 -->
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot#987
No description provided.