-
Notifications
You must be signed in to change notification settings - Fork 2k
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
release-test.yml: Fix strasbourg spelling #20008
Conversation
Small typo fix... stasbourg -> strasbourg
We can at least see that it is... fixed: broken: https://github.com/RIOT-OS/RIOT/actions/runs/6611579458/job/17955744589#step:7:11 fixed: https://github.com/RIOT-OS/RIOT/actions/runs/6611623373/job/17955881271#step:7:1 |
bors merge |
🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set. |
bors merge |
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page.
|
20013: release-test.yml: Add strasbourg creds [backport 2023.10] r=miri64 a=MrKevinWeiss # Backport of #20007 and #20008 ### Contribution description This adds creds for stasbourg needed for the `openmote-b` tests in the release specs. ### Testing procedure Hmmm... I don't know how easy it is. I will try to link results of the workflow from my personal fork maybe? ### Issues/PRs references Needed for RIOT-OS/Release-Specs#289 Co-authored-by: MrKevinWeiss <[email protected]>
Contribution description
Small typo fix... stasbourg -> strasbourg
Testing procedure
Really not easy since we need an RC to actually test it (since these tests can only be run on RCs)... but the RC1 doesn't contain the
openmote-b
fixes.Issues/PRs references