-
Notifications
You must be signed in to change notification settings - Fork 21
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.
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
fix: Change iotlabs DEFAULT_SITE to grenoble #315
base: master
Are you sure you want to change the base?
Conversation
It seems like saclay has a bunch of broken nodes on it, maybe grenoble is a bit better maintained...
If saclay doesn't get fixed soon maybe we switch. |
Here is a real test: https://github.com/RIOT-OS/RIOT/actions/runs/12887496104 |
uggg, don't be fooled by the green, all the tests were skipped due to:
|
Needs an update from the RIOT action side. |
OK there we go! |
Let's wait for this until we have proper info on some failures we have seen. |
So far all the failing ones include notes that are at the Saclay site. 4.2 and 4.4 tests samr21-xpro to iotlab-m3 ping, 4.11 and 4.12 require an nrf52840dk, 4.5 and 4.6 explicitly pick the Strasbourg site. So I think my hunch got confirmed. At least for those tests, the site needs to be fixed to Saclay, as we did for the openmotes with Strasbourg. |
eec8e0d
to
c540e46
Compare
c540e46
to
e19a4d8
Compare
OK, let's keep this in the back pocket. |
It seems like saclay has a bunch of broken nodes on it, maybe grenoble is a bit better maintained...