Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

tests/devfs: move tests-devfs out of unittests [backport 2019.07] #11858

Merged
merged 1 commit into from
Jul 17, 2019
Merged

tests/devfs: move tests-devfs out of unittests [backport 2019.07] #11858

merged 1 commit into from
Jul 17, 2019

Conversation

cladmi
Copy link
Contributor

@cladmi cladmi commented Jul 17, 2019

Backport of #11855

Contribution description

This moves unittests/tests-devfs to its own test.
It prevents requiring periph_hwrng in the unittests.

Testing procedure

I tried compiling the test with buildtest and BUILD_IN_DOCKER and all supported boards compiled. This will be tested by CI.

The test also succeeds on both native and nrf52dk locally, and should also in CI.

RIOT_CI_BUILD=1 BOARD=nrf52dk make --no-print-directory -C tests/devfs/ flash test 
RIOT_CI_BUILD=1 BOARD=nrf52dk make --no-print-directory -C tests/devfs/ flash test
Building application "tests_devfs" for "nrf52dk" with MCU "nrf52".

   text    data     bss     dec     hex filename       
  13536     244    3012   16792    4198 /home/harter/work/git/RIOT/tests/devfs/bin/nrf52dk/tests_devfs.elf
/home/harter/work/git/RIOT/dist/tools/jlink/jlink.sh flash /home/harter/work/git/RIOT/tests/devfs/bin/nrf52dk/tests_devfs.bin
### Flashing Target ###
### Flashing at base address 0x0 with offset 0 ###
SEGGER J-Link Commander V6.42d (Compiled Feb 15 2019 13:56:53)
DLL version V6.42d, compiled Feb 15 2019 13:56:43
...

Script processing completed.

/home/harter/work/git/RIOT/dist/tools/pyterm/pyterm -p "/dev/ttyACM0" -b "115200"
Twisted not available, please install it if you want to use pyterm's JSON capabilities
2019-07-17 14:45:30,462 - INFO # Connect to serial port /dev/ttyACM0
Welcome to pyterm!
Type '/exit' to exit.
2019-07-17 14:45:33,817 - INFO # main(): This is RIOT! (Version: buildtest)
2019-07-17 14:45:33,818 - INFO # ....
2019-07-17 14:45:33,819 - INFO # OK (4 tests)

The iotlab-m3 can again compile and succeed with the tests/unittests.

RIOT_CI_BUILD=1 BOARD=iotlab-m3 make -C tests/unittests/ flash test 
RIOT_CI_BUILD=1 BOARD=iotlab-m3 make -C tests/unittests/ flash test
Twisted not available, please install it if you want to use pyterm's JSON capabilities
2019-07-17 14:41:35,364 - INFO # Connect to serial port /dev/ttyUSB1
Welcome to pyterm!
Type '/exit' to exit.
2019-07-17 14:41:38,741 - INFO # �main(): This is RIOT! (Version: buildtest)
2019-07-17 14:42:39,903 - INFO # ...............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
2019-07-17 14:42:39,904 - INFO # OK (943 tests)

Issues/PRs references

unittests not compiling on iotlab-m3 was found during Release testing 2019.07-RC1
RIOT-OS/Release-Specs#128 (comment)

Splitting the test out was mentioned in the introduction PR #7421 (review)

@cladmi
tests/devfs: move tests-devfs out of unittests
5e56edb 
This moves unittests/tests-devfs to its own test.
It prevents requiring `periph_hwrng` in the `unittests`.

(cherry picked from commit 78ca09d)
@cladmi cladmi mentioned this pull request Jul 17, 2019
Merged
@miri64 miri64 self-requested a review July 17, 2019 15:11
@miri64 miri64 added Area: tests Area: tests and testing framework Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation Process: release backport Integration Process: The PR is a release backport of a change previously provided to master CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR labels Jul 17, 2019
miri64
miri64 approved these changes Jul 17, 2019
View reviewed changes
Copy link
Member

@miri64 miri64 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK. Change is identical to #11855.

@miri64 miri64 added CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR CI: run tests If set, CI server will run tests on hardware for the labeled PR and removed CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR labels Jul 17, 2019
@cladmi
Copy link
Contributor Author

cladmi commented Jul 17, 2019

I successfully re-run the testing procedure on the branch.

@miri64 miri64 merged commit 9bb8114 into RIOT-OS:2019.07-branch Jul 17, 2019
@cladmi cladmi deleted the backport/2019.07/pr/tests/unittest/split/devfs branch July 18, 2019 09:33
@cladmi cladmi mentioned this pull request Jul 18, 2019
Closed
77 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@miri64 miri64 miri64 approved these changes

Assignees
No one assigned
Labels
Area: tests Area: tests and testing framework CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR CI: run tests If set, CI server will run tests on hardware for the labeled PR Process: release backport Integration Process: The PR is a release backport of a change previously provided to master Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@cladmi @miri64