CI: test the generated Arduino library on pull requests by psiddh · Pull Request #3 · psiddh/executorch

psiddh · 2026-08-03T02:08:08Z

Summary

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that.

The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four.

verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports:

FAIL KeywordSpotting
cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11

Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install.

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that. The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four. verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports: FAIL KeywordSpotting cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11 Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install. Authored with Claude Code (Opus 5).

psiddh · 2026-08-03T02:08:08Z

Summary

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that.

The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four.

verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports:

FAIL KeywordSpotting
cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11

Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install.

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that. The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four. verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports: FAIL KeywordSpotting cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11 Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install. Authored with Claude Code (Opus 5).

psiddh · 2026-08-03T02:08:08Z

Summary

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that.

The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four.

verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports:

FAIL KeywordSpotting
cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11

Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install.

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that. The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four. verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports: FAIL KeywordSpotting cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11 Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install. Authored with Claude Code (Opus 5).

psiddh · 2026-08-03T02:08:08Z

Summary

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that.

The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four.

verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports:

FAIL KeywordSpotting
cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11

Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install.

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that. The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four. verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports: FAIL KeywordSpotting cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11 Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install. Authored with Claude Code (Opus 5).

psiddh · 2026-08-03T02:08:08Z

Summary

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that.

The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four.

verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports:

FAIL KeywordSpotting
cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11

Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install.

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that. The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four. verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports: FAIL KeywordSpotting cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11 Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install. Authored with Claude Code (Opus 5).

psiddh · 2026-08-03T02:08:08Z

Summary

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that.

The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four.

verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports:

FAIL KeywordSpotting
cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11

Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install.

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that. The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four. verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports: FAIL KeywordSpotting cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11 Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install. Authored with Claude Code (Opus 5).

psiddh · 2026-08-03T02:08:08Z

Summary

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that.

The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four.

verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports:

FAIL KeywordSpotting
cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11

Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install.

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that. The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four. verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports: FAIL KeywordSpotting cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11 Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install. Authored with Claude Code (Opus 5).

psiddh · 2026-08-03T02:08:08Z

Summary

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that.

The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four.

verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports:

FAIL KeywordSpotting
cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11

Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install.

The library is generated from this repository, so an ExecuTorch change can break it without touching examples/arduino at all. Nothing checked that. The job builds the library, verifies the shipped models against it, compiles every example for arduino:zephyr:unoq, and runs arduino-lint in Library Manager submission mode. It runs on changes under examples/arduino, backends/cortex_m, kernels/portable, runtime, and schema, which is the set that can break any of the four. verify_models.py is the part worth having. A .pte records how many values each operator call puts on the stack, and the generated kernel wrappers reject anything else; the two only agree when the model and the library came from the same commit. Cortex-M schemas change - scratch was added to the conv operators in pytorch#19636 and pytorch#19825 - and a mismatch is invisible until far too late, because the program loads, every operator resolves, and then execute returns InvalidProgram naming nothing useful. Tracking that down by hand took the better part of a day. The check compares the two directly in about a second, needs no board, and reports: FAIL KeywordSpotting cortex_m::quantized_avg_pool2d.out: model supplies 10, library expects 11 Compiling is deliberately not the whole job. Every failure worth finding in this library compiled cleanly first, so the model check runs before the sketches and arduino-lint guards the thing users actually install. Authored with Claude Code (Opus 5).

psiddh had a problem deploying to cadence August 3, 2026 02:08 — with GitHub Actions Error

psiddh force-pushed the arduino-library-ci branch from d9e8a1b to 9c47065Compare August 3, 2026 18:10

psiddh had a problem deploying to cadence August 3, 2026 18:10 — with GitHub Actions Error

psiddh force-pushed the arduino-library-ci branch from 9c47065 to 735cc92Compare August 3, 2026 18:11

psiddh had a problem deploying to cadence August 3, 2026 18:11 — with GitHub Actions Error

psiddh force-pushed the arduino-library-ci branch from 735cc92 to 545e848Compare August 4, 2026 17:44

psiddh had a problem deploying to cadence August 4, 2026 17:44 — with GitHub Actions Error