+1 here, big thank you!! :-)

=== NOTES ===

* STM32 builds are fixed, thank you!! :-)
* There still seems to be this warning for all targets at
./tools/configure.sh stage "boards/Kconfig:5602:warning: leading
whitespace ignored". That does not influence build/runtime.
* Build logs pack attached, full logs url provided for each tested target.

=== BUILD HOST ===

FreeBSD hexagon 14.4-RELEASE-p7 FreeBSD 14.4-RELEASE-p7 #0 -dirty: Tue
Jun 30 08:53:56 UTC 2026
[email protected]:/usr/obj/usr/src/amd64.amd64/sys/GENERIC
amd64

=== TARGETS ===

1. STM32L432KC
  * PASS (FIXED).
  * boards/Kconfig:5602:warning: leading whitespace ignored.
  * https://gist.github.com/cederom/8fb18f4e6da40ea8cf5c2f28e535216f.

2. STM32H745ZI
  * PASS (FIXED).
  * only build tested, no runtime, have h755 board not h745 that does not flash.
  * https://gist.github.com/cederom/ccbd0737161da6932a3bf86bd10724ac.

3. STM32F769I
  * PASS (FIXED).
  * boards/Kconfig:5602:warning: leading whitespace ignored.
  * https://gist.github.com/cederom/59bbbe511d6fb58552a6175ba951ee42.

4. STM32F412RE
  * PASS.
  * boards/Kconfig:5602:warning: leading whitespace ignored.
  * https://gist.github.com/cederom/40ed7c4410657a7c07f9643b9286078d.

5. STM32F411RE
  * PASS.
  * boards/Kconfig:5602:warning: leading whitespace ignored.
  * https://gist.github.com/cederom/88a397f1a0029af76eab6605322a02f9.

6. STM32F072RB
  * PASS (FIXED).
  * boards/Kconfig:5602:warning: leading whitespace ignored.
  * only build tested, no runtime.
  * https://gist.github.com/cederom/11a67aec2f6836191640d380ab0827e2.

7. SPRESENSE
  * PASS.
  * boards/Kconfig:5602:warning: leading whitespace ignored.
  * https://gist.github.com/cederom/2d86a91109cab2f5dc8c98974e18195f.

8. SAMv71
 * PASS.
 * boards/Kconfig:5602:warning: leading whitespace ignored.
 * https://gist.github.com/cederom/cd6d9be456ce6d5c5a0eaec0ce30c647.

9. rPI-PICO
  * PASS (remembering previous issues).
  * boards/Kconfig:5602:warning: leading whitespace ignored.
  * ostest takes >4min to getprime but passes.
  * https://gist.github.com/cederom/9291c87bed7e15d8a25ce9750c239bb4.

10. rPI-PICO-2
  * FAIL (no change).
  * boards/Kconfig:5602:warning: leading whitespace ignored.
  * usbnsh does not enumerate serial port.
  * https://gist.github.com/cederom/431754d3602f0b8dedda4d5c9a851e0c.

11. rPI-4B
  * PASS.
  * boards/Kconfig:5602:warning: leading whitespace ignored.
  * https://gist.github.com/cederom/9a5a14f2d81a071a080566ee12e8602e.

12. ESP32S3
  * PASS.
  * boards/Kconfig:5602:warning: leading whitespace ignored.
  * Warning: DEPRECATED: 'esptool.py' is deprecated. Please use
'esptool' instead. The '.py' suffix will be removed in a future major
release.
  * Warning: Deprecated: Command 'write_flash' is deprecated. Use
'write-flash' instead.
  * https://gist.github.com/cederom/aee87195655e347b82e16fed38649d55.

13. ESP32C6
  * PASS.
  * boards/Kconfig:5602:warning: leading whitespace ignored.
  * Warning: DEPRECATED: 'esptool.py' is deprecated. Please use
'esptool' instead. The '.py' suffix will be removed in a future major
release.
  * Warning: Deprecated: Command 'write_flash' is deprecated. Use
'write-flash' instead.
  * https://gist.github.com/cederom/29334669163340012361a537459e562b.

14. ESP32C3
  * PASS.
  * boards/Kconfig:5602:warning: leading whitespace ignored.
  * https://gist.github.com/cederom/74f84d837fec2a6814b59c08bdba1965.

15. ESP32
  * PASS.
  * boards/Kconfig:5602:warning: leading whitespace ignored.
  * Warning: DEPRECATED: 'esptool.py' is deprecated. Please use
'esptool' instead. The '.py' suffix will be removed in a future major
release.
  * Warning: Deprecated: Command 'write_flash' is deprecated. Use
'write-flash' instead.
  * https://gist.github.com/cederom/19ecc6a745d464bac36e46ab2913710a

--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info





On Mon, Jul 6, 2026 at 3:33 PM Alin Jerpelea <[email protected]> wrote:
>
> Hello all,
> Apache NuttX 13.0.0 RC2 has been staged under [1] and it's
> time to vote on accepting it for release. Voting will be open for 72hr.
>
> A minimum of 3 binding +1 votes and more binding +1 than binding -1 are
> required to pass.
>
> The Apache requirements for approving a release can be found here [3]
> "Before voting +1 PMC members are required to download the signed
> source code package, compile it as provided, and test the resulting
> executable on their own platform, along with also verifying that the
> package meets the requirements of the ASF policy on releases."
>
> A document to walk through some of this process has been published on
> our project wiki and can be found here [4].
>
> [ ] +1 accept (indicate what you validated - e.g. performed the non-RM
> items in [4])
> [ ] -1 reject (explanation required)
>
> Thank you all,
> Alin Jerpelea
>
> SCM Information:
>   Release tag: nuttx-13.0.0-RC2
>   Hash for the release nuttx tag: f5291a8df19660fc69992c0763e1a4cc87b7037c
>   Hash for the release nuttx-apps tag:
> 20ffb1a3a3b590d52890ee865a28442390e5d16c
>
> [1] https://dist.apache.org/repos/dist/dev/nuttx/13.0.0-RC2/
> [2]
> https://raw.githubusercontent.com/apache/nuttx/nuttx-13.0.0-RC2/ReleaseNotes
> [3] https://www.apache.org/dev/release.html#approving-a-release
> [4]
> https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release

Attachment: cederom-nxreltest-13.0.0-RC2.tar.xz
Description: application/xz

Reply via email to