Closed chrysn closed 2 years ago
Ticking off "Task #01 - Compile test" as the last commit on the release branch passed a murdock run that did not seem to skip any tests.
Tests ran manually on iotlab-m3:
$ BOARD=iotlab-m3 IOTLAB_NODES=1 IOTLAB_DURATION=10 make iotlab-exp -C tests/tests_unittests
$ iotlab-experiment get -n
[...] m3-101.grenoble.iot-lab.info
$ BOARD=iotlab-m3 IOTLAB_NODE=m3-101.grenoble.iot-lab.info make all flash test -C tests/tests_unittests
$ BOARD=iotlab-m3 IOTLAB_NODE=(actually a different experiment) ./dist/tools/compile_and_test_for_board/compile_and_test_for_board.py . iotlab-m3
This is ongoing, and I'll tick off 02-tests / "Task #02 - Subset of tests on iotlab-m3" when that's done.
I've run through the native tests (compile-and-test), with some failures -- but AFAICT they were all related to odd versions of compilers used here:
protoc
) were missing.Except for the 18480 issue, I consider these good enough. If that turns out to be a false positive, I'll tick the "build on native" box.
Going through the native tests, they worked except
I consider these tests good enough to tick the "native" box.
At iotlab-m3, local building and testing-at-IoT-LAB worked except:
A few tests failed (but hey, this is already running all runnable ones rather than "a subset of"; still):
Up to be investigated are still:
both of which fail in repeated tests on m3-100.grenoble.iot-lab.info.
(all done in manual runs like BOARD=iotlab-m3 IOTLAB_NODE=m3-100.grenoble.iot-lab.info make flash reset test -C tests/...
)
With the above boxes ticked, some things are left to do in tests cleanup, but none of that is release critical; ticking the iotlab-m3 box.
Closing in favor of #258
This issue lists the status of all tests for the Release Candidate 3 of the 2022.07 release.
Specs tested:
Task #09 - deprecatedTask #10 - deprecated