Hi Matteo: Wonder if the NuttX Build History will help? For every past build, it shows the Commit Hashes for the NuttX Repo and NuttX Apps:
https://nuttx-dashboard.org/d/fe2q876wubc3kc/nuttx-build-history?from=now-6M&to=now&timezone=browser&var-arch=$__all&var-subarch=$__all&var-board=w5500-evb-pico&var-config=usbnsh&var-group=$__all&var-Filters= 2 issues though: (1) The historical data is kept only for the past 16 days (2) I need to provide a scriptable way to export the data Lup On Fri, Jan 17, 2025 at 5:49 AM Matteo Golin <matteo.go...@gmail.com> wrote: > Hello everyone, > > I am working on this issue about the W5500-EVB-Pico: > https://github.com/apache/nuttx/issues/15549 > > I need to get the USB shell working since we are using this board as the > controller for our hybrid rocket motor system. > I am attempting to locate the commit breaking the shell using `git > bisect`, but I am encountering a pretty big issue > with the method I am using. > > When bisecting, sometimes the commits get rolled back far enough that the > current version of NuttX apps breaks the build > on an application. My method so far was to use `git log` to figure out the > date of the commit that I am building and > checkout the NuttX apps to a commit of a roughly similar date. However, > this approach is still leading me to failing > builds because of the apps directory not being exactly in sync with the > kernel, and it is tedious to figure out which > commit works. > > I am having a similar problem because this board depends on the Pico SDK > being of a certain version, but that is much > easier since I am able to just check out to a specific version like 1.4.0 > and rebuild. > > Anyone who regularly bisects on NuttX, can you tell me how you get around > this issue? > > -- > Matteo Golin >
