Since some boards an int is 16 bits the atoi truncates values.
This commit using a long instead of an int.

This states iotlab boards shouldn't run these tests.
This is because the i2c address of L3G4200 is the same ad the ds1307.
This causes an error that thinks the test is valid when it is not.

* drivers/ccs811: fix types in debug messages

* drivers/driver_ccs811_full: fix unused variable build error

Co-authored-by: Federico Pellegrin <fede@evolware.org>

The tests overrides the target all to be tested by the CI.
All the instructions how to use it are in README.md
The test is successful if the image boots and displays
information about the image and running slot.

Co-authored-by: Federico Pellegrin <fede@evolware.org>

Otherwise it may break on nrf51 boards where the timeout can be slightly above 100. Using 105us margin seems enough

Otherwise it raises a timeout on slow boards. It takes around 2 minutes
on nrf51 based boards (e.g microbit)

On a microbit (nrf51) the autotest takes around 4 minutes to complete.

Otherwise the test takes too long on nrf51 based boards and fails:
- 80s on a microbit for tests/pkg_micro-ecc
- 120s on a microbit for tests/pkg_micro-ecc-with-hwrng

It can takes up to 640s to complete on microbit

This will allow testing the build system 'utils' functions.

Without the protection, the host system also tries to execute the tests.

Without the protection, the host system also tries to execute the tests.

If the file does not exist, because of concurrency issues, there is no
error. So verify it is there for good measures.

The test randomly fails for unrelated PRs. Expecting real-time timing on
native is not really possible. Maybe it could be fixed but it currently
triggers many false positive.

The test randomly fails for unrelated PRs. Expecting real-time timing on
native is not really possible. Maybe it could be fixed but it currently
triggers many false positive.

Unittest for riotboot_hdr submodule. If successful, it must
print 4 successful tests.

Tests are based on the tests vectors provided in RFC 7539