CeDeROM

Another problem is that people very often send unfinished undescribed PRs that are updated without a comment or request that triggers whole big CI process several times :-( Some changes...

> @cederom Maybe our PRs should have a Mandatory Field: Which NuttX Config to build, e.g. `rv-virt:nsh`. Then the CI Workflow should do `tools/configure.sh rv-virt:nsh && make`. Before starting the...

So it looks like for now, where dramatic steps need to be taken, we need to mark all PR as drafts and start CI by hand when we are sure...

Okay its 0000UTC. We are really short on time. I have merged changes. Lets monitor the use now for 24h we need metrics. We can always revert the commits. Looking...

Sorry no clue why it closed in my name o_O Ah, GH seems to close issues on its own when related PR gets merged. Probably this also happened before when...

> @lupyuen: (2) Can we have Restartable Builds? Doesn't quite make sense to build everything from scratch (arm6, arm7, riscv7) just because one job failed (xtensa2) It is possible to...

Sounds like a repo clone that will verify nuttx and nuttx-apps master independently twice a day?

> Can anyone help me understand why the workflow is failing? What should I do to fix it? Looks like internal CI problem, builds fine for me on FreeBSD :-)

* I just got this problem. * There are TONS of scripts out there that used `pip install package==` syntax for years. * You **broke the backward compatibility** in a...

You "unintentionally" broke the command that was working fine for years. Why not just bring it back? Win-Win: You can easily bring back `pip install package==` as an alias to...