Skip to content
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

Poo#19230 Stabilize patch before migration tests on PPC by typing slowly #2976

Closed

Conversation

rwx788
Copy link
Member

@rwx788 rwx788 commented May 30, 2017

In couple of runs redirection key was not properly typed, in other runs shift key was still pressed and wrong serial device was used. Issue occurs only on PowerPC and is not reproducible in every run. By typing unstable command slower we should gain more stability.

Progress ticket: https://progress.opensuse.org/issues/19230
Verification run: http://10.160.66.147/tests/216#step/patch_before_migration/16

@rwx788 rwx788 changed the title Poo#19230 Stabilize patch before migration tests by typing slowly Poo#19230 Stabilize patch before migration tests on PPC by typing slowly May 30, 2017
@rwx788 rwx788 force-pushed the poo#19230_patch_before_migration branch from 6da9974 to 637d081 Compare May 30, 2017 09:00
@@ -332,7 +332,7 @@ sub wait_boot {
elsif (match_has_tag('inst-bootmenu')) {
# assuming the cursor is on 'installation' by default and 'boot from
# harddisk' is above
send_key_until_needlematch 'inst-bootmenu-boot-harddisk', 'up';
# send_key_until_needlematch 'inst-bootmenu-boot-harddisk', 'up';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's probably only for testing, right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, sorry, this was accidentally committed.

my ($type_slow) = @_;
my $yast_scc_cmd = "yast2 scc; echo yast-scc-done-\$?- > /dev/$serialdev\n";
#Due to ninja keys on PPC, may be required to type command slowlier, see poo#19230
if ($type_slow) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you have an idea why we should type slower in this specific case and not in general? There is also the variable VNC_TYPING_LIMIT to limit overall typing speed. And we have set this for ppc64le already so maybe we really need to lower the limit. Unless it was about "QA-Power-…" behaving weird, which is another progress ticket

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, tests on malbec are much more stable. Exactly this line failed couple of times due to redirection symbol, which requires shift key, other strings seem to work fine. This is same case when alt key is pressed and sometimes not released before. In general this change has to be reverted once it is fixed in framework, as I believe it should work even if worker is slow.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we still have no idea if this is broken in qemu, power kernel or firmware - and that it's machine specific does not really give good an impression on the architecture :(

But just as okurz said, changing our tests because one worker is broken doesn't sound like a fair deal. Set the VNC_TYPING_LIMIT to really, really slow on that one worker.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, changing VNC_TYPING_LIMIT is better idea as may help with other test failures like one here: https://progress.opensuse.org/issues/19266 https://progress.opensuse.org/issues/19414 which never happened on malbec.

@@ -20,7 +20,7 @@ sub is_smt_or_module_tests {
}

sub system_prepare() {
select_console 'root-console';
select_console('root-console');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why change? I think we should avoid reworking unrelated sections when it's not adding real value

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the comment, missed this change also, will revert it.

@rwx788 rwx788 changed the title Poo#19230 Stabilize patch before migration tests on PPC by typing slowly [WIP] Poo#19230 Stabilize patch before migration tests on PPC by typing slowly May 30, 2017
@rwx788 rwx788 force-pushed the poo#19230_patch_before_migration branch from 637d081 to 1ce5510 Compare May 30, 2017 09:20
@rwx788 rwx788 changed the title [WIP] Poo#19230 Stabilize patch before migration tests on PPC by typing slowly Poo#19230 Stabilize patch before migration tests on PPC by typing slowly May 30, 2017
@rwx788 rwx788 changed the title Poo#19230 Stabilize patch before migration tests on PPC by typing slowly [WIP]Poo#19230 Stabilize patch before migration tests on PPC by typing slowly May 30, 2017
In couple of runs redirection key was not properly typed, in other runs
shift key was still pressed and wrong serial device was used. Issue
occurs only on PowerPC and is not reproducible in every run. By typing
unstable command slower we should gain more stability.
@rwx788 rwx788 force-pushed the poo#19230_patch_before_migration branch from 1ce5510 to ffd108c Compare May 30, 2017 09:33
@rwx788 rwx788 changed the title [WIP]Poo#19230 Stabilize patch before migration tests on PPC by typing slowly Poo#19230 Stabilize patch before migration tests on PPC by typing slowly May 30, 2017
@rwx788
Copy link
Member Author

rwx788 commented May 30, 2017

Trying with VNC_TYPING_LIMIT option and finding out real root cause instead of doing workaround for single worker.

@rwx788 rwx788 closed this May 30, 2017
@rwx788 rwx788 deleted the poo#19230_patch_before_migration branch July 12, 2017 07:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants