ci: skip flash_qemu_psram as we test it with the unamalgamated build
What changed, and why it matters
This commit only changes a GitLab CI configuration file. It comments out one automated test job (flash_qemu_psram) because the same scenario is already tested by another job (flash_qemu_psram_unamalgamated). There is no change to the actual Jade firmware, wallet code, cryptography, or anything users interact with. It is purely a pipeline optimization to avoid redundant testing.
No security action needed. This is a routine CI maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies gitlab/flash.yml, a GitLab CI pipeline definition. It comments out the flash_qemu_psram job, which depended on test_libjade and build_test_qemu_psram, leaving flash_qemu_psram_unamalgamated in place. The commit message states this is because the unamalgamated build already covers the same case. No source code, build artifacts, firmware logic, or security-sensitive configuration is altered.
Changed components
GitLab CI pipeline definition (gitlab/flash.yml)Inspect captured patch +4 / −3
diff --git a/gitlab/flash.yml b/gitlab/flash.yml
index 7c25ed1..1d0f83c 100644
--- a/gitlab/flash.yml
+++ b/gitlab/flash.yml
@@ -20,9 +20,10 @@ flash_qemu:
extends: .flash_qemu_template
needs: [ test_libjade, build_test_qemu ]
-flash_qemu_psram:
- extends: .flash_qemu_template
- needs: [ test_libjade, build_test_qemu_psram ]
+# Skip flashing this as its covered by the unamalgamated case
+#flash_qemu_psram:
+# extends: .flash_qemu_template
+# needs: [ test_libjade, build_test_qemu_psram ]
flash_qemu_psram_unamalgamated:
extends: .flash_qemu_template
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.