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

[Tracking] Fix failures of test-on-iotlab #20791

Open
mguetschow opened this issue Jul 18, 2024 · 1 comment
Open

[Tracking] Fix failures of test-on-iotlab #20791

mguetschow opened this issue Jul 18, 2024 · 1 comment
Labels
Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) Type: tracking The issue tracks and organizes the sub-tasks of a larger effort

Comments

@mguetschow
Copy link
Contributor

Description

Several tests have been failing for quite some time on specific boards in the test-on-iotlab action. They are not strictly part of the release-specs task02 as of now, but do indicate bugs in RIOT for specific boards. This issue collects constantly failing test-board combinations and should be used to coordinate fixing.

ERROR:dwm1001:Tests failed: 3
Failures during test:
- [tests/periph/timer_periodic](tests/periph/timer_periodic/test.failed)
- [tests/pkg/lz4](tests/pkg/lz4/test.failed)
- [tests/pkg/uzlib](tests/pkg/uzlib/test.failed)

ERROR:iotlab-m3:Tests failed: 3
Failures during test:
- [tests/drivers/mtd_flashpage](tests/drivers/mtd_flashpage/test.failed)
- [tests/net/gcoap_dns](tests/net/gcoap_dns/test.failed)
- [tests/pkg/libschc](tests/pkg/libschc/test.failed)

ERROR:nrf52dk:Tests failed: 5
Failures during test:
- [tests/pkg/lz4](tests/pkg/lz4/test.failed)
- [tests/pkg/uzlib](tests/pkg/uzlib/test.failed)
- [tests/sys/congure_abe](tests/sys/congure_abe/test.failed)
Failures during test.flash:
- [tests/sys/cb_mux_bench](tests/sys/cb_mux_bench/test.flash.failed)
- [tests/sys/xtimer_hang](tests/sys/xtimer_hang/test.flash.failed)

ERROR:samr34-xpro:Tests failed: 4
Failures during compilation:
- [tests/turo_txt](tests/turo_txt/compilation.failed)
Failures during test:
- [tests/drivers/mtd_raw](tests/drivers/mtd_raw/test.failed)
- [tests/periph/rtt](tests/periph/rtt/test.failed)
- [tests/sys/dbgpin](tests/sys/dbgpin/test.failed)

ERROR:b-l072z-lrwan1:Tests failed: 1
Failures during test:
- [tests/pkg/libschc](tests/pkg/libschc/test.failed)

The failure during compilation on the samr34-xpro was apparently due to insufficient space on the action runner. Not sure how to cope with this.

Useful links

The list was initially compiled from the Workflow Action on the 2024.07-RC1, and has been compared to several recent master and the 2024.04-RC2 workflow.
@mguetschow mguetschow added Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) Type: tracking The issue tracks and organizes the sub-tasks of a larger effort labels Jul 18, 2024
@mguetschow mguetschow mentioned this issue Jul 18, 2024
Closed
86 tasks
@MrKevinWeiss
Copy link
Contributor

I think tests/periph/timer_periodic and tests/pkg/libschc have always been flakey or failing with IoTLabs. I should look at tests/turo_txt. I thought the mtd ones were fixed but maybe not... I can take a closer look on Monday :)

@mguetschow mguetschow mentioned this issue Nov 14, 2024
Closed
86 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type: bug The issue reports a bug / The PR fixes a bug (including spelling errors) Type: tracking The issue tracks and organizes the sub-tasks of a larger effort
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MrKevinWeiss @mguetschow