-
Notifications
You must be signed in to change notification settings - Fork 164
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
[12.0-stable] pillar/assignableadapters: clear error strings #4240
[12.0-stable] pillar/assignableadapters: clear error strings #4240
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.
Could you please use the -x
when cherry-picking commits?
It's minor. Rather than that - fine.
lol, why does Yetus scream only here... |
60dbfb6
to
93381b6
Compare
@christoph-zededa don't we have to port it into 11.0-stable? |
I don't see the affected code in |
@christoph-zededa can we close this PR for now, if you want to replace it with a new one? |
I will use this PR, but now it is in draft. |
50e1918
to
d91b31c
Compare
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.
Could you please take the commit hash from the master branch, not from the original feature branch?
for usb collisions: 1. create two usb adapters with collision 2. change the usbaddr of one of the adapters now the collision should be gone, but as the error string for both adapters has been set, it was not cleared for parentassigngrp cycles: 1. create two usb adapters that have each other as parentassigngrp 2. change the parentassignrp of one of the adapters now the cycle should be gone, but as the error string for both adapters has been set, it was not cleared Also don't overwrite errors and be able to clear specific error types Signed-off-by: Christoph Ostarek <[email protected]> (cherry picked from commit d1e13b8)
d91b31c
to
1b8e10d
Compare
done |
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.
Let's ignore the Yetus complaints, as the commit cherry-picked one-to-one.
Running the tests
now the collision should be gone, but
as the error string for both adapters has been set, it was not cleared