-
Notifications
You must be signed in to change notification settings - Fork 276
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
Bump $count in calls to send_key_until_needlematch #15404
Bump $count in calls to send_key_until_needlematch #15404
Conversation
Great PR! Please pay attention to the following items before merging: Files matching
This is an automatically generated QA checklist based on modified files |
32d1977
to
b7a04e2
Compare
b7a04e2
to
f107f2c
Compare
The function send_key_until_needlematch() had an off-by-one error. This error has been fixed recently, so we need to increment +1 the $count argument (3rd) in all test suite calling it.
f107f2c
to
5bda96c
Compare
Have all of these calls really been made under the assumption that send_key_until_needlematch works like it did before os-autoinst/os-autoinst#2151? To me that PR seems to "fix" something in the sense that most people would have expected that behavior anyways. However, if that is not true, I'm wondering about the usefulness of os-autoinst/os-autoinst#2151. |
I guess nobody can tell if ALL the calls are made with some expectation or the other. Most of them are likely to be "N-1 bug aware", where you can see some key are sent 9 times or 19 times example1, example2 when an EVEN number of keys are required. Starting motivation of os-autoinst/os-autoinst#2151 and related POO ticket is to make the testapi function behave as user expects, e.g. you ask to send a key up to 3 times, it sends the key up to 3 times, and not 4. Once we got that fixed (and merged), we should update accordingly the calling code. What do you think? |
Ok, and more a decision of test writers anyways. |
The function
send_key_until_needlematch()
had an off-by-one error.This error has been recently fixed, so we need to increment +1 the
$count
argument (3rd positional) in all test suites calling it.