This
* renames DEFAULT_xID to USB_xID_TESTING as it is not really a default
(if anyting, the 7D00 is, and it's not that)
* moves the check into Makefile
* generalizes the check to all test PID/VID pairs
* in doing so, fixes the "or" (which would have ruled out warning-free
use of an allocated pid.codes number), and compares to the actual
testing PID rather than the RIOT-peripheral PID
* removes all occurrences of duplicated checks in examples or tests,
leaving definitions only where they are needed
* moves the Kconfig defaults of the usbus_minimal example into the main
Kconfig, as these are good defaults for all cases when USB is enabled
manually
Closes: https://github.com/RIOT-OS/RIOT/issues/12273
When building with make -j, flatbuffers is cloned by both the flatc build and the regular package build and from time to time a concurrency issue make the build to fail. Keeping regular flatbuffer package and flatc tool sources separate avoid this issue
Previously, uncrustify.sh would fail (report uncrustifying necessary) if
there was any output of uncrustify. Turns out uncrustify sometimes
outputs something.
This commit changes the logic to use uncrustify's output value as
indicator.
Also, adds printing which file causes the check to fail.
When the child has a clean-up step (closing files, killing
sub-processes, deleting operational files, etc.), this currently is not
executed by the test, as the `testrunner` just does a hard `SIGKILL`
for the child's PPID. This change makes this a `SIGTERM` and only uses
`SIGKILL` if there are still processes lingering a second after the
`SIGTERM`.
This adds a new subdirectory called `fuzzing/` which will contain
applications for fuzzing various RIOT network modules in the future.
This subdirectory is heavily inspired by the `examples/` subdirectory.
The fuzzing applications use AFL as a fuzzer. Each application contains
Makefiles, source code, and an input corpus used by AFL to generate
input for fuzzing.
The `start_network.sh` script creates a `${TUN}` interface, so
the `${TAP}` variable will always be empty.
This means start_dhcpd() will always fail as the DHCPv6 script is lacking
an interface.
Previously, when the creation of the TUN/TAP interface failed in one of
the `start_network.sh` scripts, the script will fail with a cryptic
error like
> dist/tools/ethos/start_network.sh: 68: [: -eq: unexpected operator
This fix ensures, that the value of this variable checked is always set
such that in the error case, `ethos`/`sliptty` won't start.
