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

gh_action/test-on-iotlab: update available boards #18303

Merged
merged 1 commit into from
Jul 11, 2022
Merged

gh_action/test-on-iotlab: update available boards #18303

merged 1 commit into from
Jul 11, 2022

Conversation

aabadie
Copy link
Contributor

@aabadie aabadie commented Jul 7, 2022

Contribution description

After today's maintenance on IoT-LAB some boards are no longer available on the Saclay site and some are now only available in Lille. This PR updates the test-on-iotlab build matrix to reflect that change.

Testing procedure

  • test-on-iotlab should run as expected, e.g use dwm1001 from lille and don't build on nrf51dk and nrf52832mdk

Issues/PRs references

None

@github-actions github-actions bot added the Area: CI Area: Continuous Integration of RIOT components label Jul 7, 2022
@aabadie
Copy link
Contributor Author

aabadie commented Jul 7, 2022

I started a manual workflow that can be followed here

@aabadie
Copy link
Contributor Author

aabadie commented Jul 7, 2022

I started a manual workflow that can be followed here

So far, it works as expected (but it might fail in the end for different reasons)

@aabadie aabadie added CI: skip compile test If set, CI server will run only non-compile jobs, but no compile jobs or their dependent jobs CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR labels Jul 7, 2022
@fjmolinas
Copy link
Contributor

Just out of curiosity @aabadie what happened to the BOARDs in Saclay?

@aabadie
Copy link
Contributor Author

aabadie commented Jul 8, 2022 •
edited
Loading

Just out of curiosity @aabadie what happened to the BOARDs in Saclay?

dwm1001, nrf52840-mdk, nrf52832-mdk, microbit, phynode and pycom were removed. For dwm1001, some others are deployed in Lille. For pycom, there are 30 deployed in Strasbourg.
I know you were using the dwm1001 in Saclay but with the ongoing "refactoring" planned in the building we can't keep the deployment in one of the room (in Digiteo 1) as it was.

@miri64 miri64 added the Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation label Jul 11, 2022
@miri64
Copy link
Member

miri64 commented Jul 11, 2022

I started a manual workflow that can be followed here

Dead link, but I trust that this was tested properly.

@miri64 miri64 merged commit 747aac2 into RIOT-OS:master Jul 11, 2022
@aabadie aabadie deleted the pr/ci/test-on-iotlab-update branch July 11, 2022 10:31
@chrysn chrysn added this to the Release 2022.07 milestone Aug 25, 2022
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: CI Area: Continuous Integration of RIOT components CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR CI: skip compile test If set, CI server will run only non-compile jobs, but no compile jobs or their dependent jobs Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation
Projects
None yet
Milestone
Release 2022.07
Development

Successfully merging this pull request may close these issues.
4 participants
@aabadie @fjmolinas @miri64 @chrysn