Repository navigation
ci: split e2e into fast slice job + slow P3 firmware job - #106
Conversation
e2e-slice: installs PrusaSlicer, slices model, runs p2pp, lints output (~2 min) e2e-p3-firmware: downloads 405MB firmware, QEMU ARM setup, P3 acceptance (slow, best-effort) This gives fast feedback on slice/p2pp/lint while P3 firmware runs in parallel. P2PP_SKIP_P3 env var lets e2e_pipeline.sh skip the simulator stage.
There was a problem hiding this comment.
Stale comment
Approved. Cursor Bugbot and Cursor Security Agent were not present after the initial check poll, so those signals were skipped; no applicable approval policies required human review, and this automation had no prior approval. No reviewers were assigned.
Sent by Cursor Approval Agent: Pull Request Router and Approver
There was a problem hiding this comment.
Stale comment
Approved. Cursor Bugbot and Cursor Security Agent were not present after the initial check poll, so those signals were skipped; no applicable approval policies required human review, and this automation had no current approval to keep. No reviewers were assigned.
Sent by Cursor Approval Agent: Pull Request Router and Approver
There was a problem hiding this comment.
Approved. Cursor Bugbot and Cursor Security Agent were not present after the initial check poll, so those signals were skipped; no applicable approval policies required human review, and this automation had no current approval to keep. No reviewers were assigned.
Sent by Cursor Approval Agent: Pull Request Router and Approver


Splits the e2e pipeline into two parallel jobs:
e2e-slice (fast, ~2 min): PrusaSlicer → p2pp → lint
e2e-p3-firmware (slow, best-effort): 405MB firmware download → QEMU → P3 acceptance
This gives fast CI feedback on the core pipeline while the P3 firmware runs separately.
P3 firmware job is continue-on-error since it takes 20+ minutes on first run (no cache).