On Thu, Jul 31, 2025 at 09:58:27AM +0000, Christoph Niedermaier wrote: > From: Tom Rini <tr...@konsulko.com> > Sent: Monday, July 28, 2025 9:03 PM > > On Fri, Jul 18, 2025 at 07:05:58PM +0200, Christoph Niedermaier wrote: > > > >> Add the "-l" parameter to the "env select" command to print the available > >> environment targets, convert all argument parsing in the file nvedit.c to > >> getopt() and check that with unit tests. > >> > >> The first patch converts the parsing of arguments to getopt() for all env > >> commands. The second one avoids stopping unit test on console output > >> "## Error: ". The third one adds unit tests for checking the env command. > >> These were used to check the env commands before and after the conversion. > >> The fourth patch adds the actual new parameter "-l" for the "env select" > >> command. > >> > >> Christoph Niedermaier (3): > >> cmd: nvedit: Convert the parsing of arguments to getopt() > >> test/py: Avoid stopping the test on console output "## Error: " > >> test: cmd: nvedit: Add basic unit tests > >> cmd: env: select: Add output for available environment targets > > > > I'm sorry, but it seems like a lot of the tests fail in CI? > > https://source.denx.de/u-boot/u-boot/-/jobs/1209804 > > https://source.denx.de/u-boot/u-boot/-/jobs/1209794 > > For example. > > I think I fixed my test, but broke other tests in the process. > I'm very sorry. I will try to fix the problem, but it is difficult > to reproduce the entire CI locally. I will try my best, sorry again.
You can trigger CI runs too via GitHub / Azure, BTW: https://docs.u-boot.org/en/latest/develop/ci_testing.html -- Tom
signature.asc
Description: PGP signature
