-
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
tests: mutex_order: updated test and fixed README #6051
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK
4: 4, | ||
5: 0, | ||
6: 2, | ||
7: 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To dependend on the C code IMHO, but let's get this merged ASAP.
I would recommend to only provide a backport after #6050 was merged so you don't have to rebase ;-) |
Output and README.md correlate now. The python script isn't very helpful as it is. A statement "SUCCESS/FAILED" is missing. Also, |
@A-Paul pexpect fails with an exception if the output is wrong, so you definitely will notice ;-) |
Murdock fail due to #6036. Go. |
Please provide a backport, I want to have an RC tomorrow morning (preferably with this and a backport of #6053). |
For a moment I was really afraid that you are serious about that. |
The README of this test is incorrect. Furthermore, the test includes an unnecessary dependency to
xtimer
. As a bonus feature this PR also includes an according pexpect script for this test.