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

Use mouse to login gdm if username is not highlighted. #13009

Merged
merged 1 commit into from Aug 4, 2021

Conversation

zhaocongjia
Copy link
Contributor

And remove the softfailure.
Upstream has changed the design of gdm, although the first
username in gdm is highlighted after boot, it is not always
like that under other circumstance. So when the username
is not highlighted, use 'assert_and_click'.

Also update dm_login a bit to avoid using hard-coded value and remove outdated comment.

And remove the softfailure.
Upstream has changed the desgin of gdm, although the first
username in gdm is highlighted after boot, it is not always
like that under other circumstance.  So when the username
is not highlighted, use 'assert_and_click'.

https://progress.opensuse.org/issues/64947
@GraceWang571
Copy link
Contributor

Does the code change work on the previous release (e.g. SLE12SP5 or SLE15SP3...)?
We need to make sure the code change won't break the maintenance test.

@zhaocongjia
Copy link
Contributor Author

Basically, this commit just removes a softfailure, which only happens sporadically. So this should not break any older releases.

@GraceWang571
Copy link
Contributor

Basically, this commit just removes a softfailure, which only happens sporadically. So this should not break any older releases.

Yeah, the thing is that we need to make sure the bsc#1086425 is really fixed on the potentially affected versions (e.g. TW, Leap, and SLE). That's to say, the status of bsc#1086425 is VERIFIED FIXED.
And then, we are safe to remove the softfailure here.

@zhaocongjia
Copy link
Contributor Author

bsc#1086425 is fixed -- username is highlighted in gdm, but that is not stable for our testing purpose -- if the mouse cursor changes a little or if we switch console, then the focus can be lost. So in testing we should use mouse as a fallback and don't consider this as softfail.

@GraceWang571
Copy link
Contributor

I know we can see from the https://openqa.suse.de/tests/6631109/file/autoinst-log.txt that the mouse_set code is gone.
But the gdm_session_switch is not enabled for TW, so it might not be a good choice to use https://openqa.opensuse.org/tests/1865638 as a verification run for TW.

In terms of the softfailure part, it would be better to use https://openqa.suse.de/tests/6599163#step/first_boot/6 since it's still marked as softfailure due to bsc#1086425. Run the test suite with your code change and see if the softfailure disappears, and see if there are any side-effect.

@zhaocongjia
Copy link
Contributor Author

There seems no such softfail on TW.

The updated VR on SLE is: https://openqa.suse.de/tests/6645210#step/first_boot/5

@GraceWang571 GraceWang571 merged commit cf2efd0 into os-autoinst:master Aug 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants