observation¶

What happens is that when the autoyast profile is wrong or not found, the tests keep trying to match needles and continue.

One such case is [0]. The problem appears something like 5 minutes after it starts but keeps running for 2h where the job time limits are reached.
Because this cause a slow feedback loop of the tests, in combination of the resources which are occupied without any good reason i would like to propose a solution.

the easier would be to match a needle with the popup and abort.
I dont know if there is already a module for it but we could run a check on the xml profile before installation module. I am not sure but i think there was something implemented for this specific reason.

To reproduce:
you can use https://gist.github.com/b10n1k/bca22757c5e4eb11473ceda30820f6d2 as profile.xml

Actual results:
http://aquarius.suse.cz/tests/11324#step/installation/2

Expected:
i am not sure about that. should that be one of the following:

• Exit after some rational time when the error exists.
• terminate needle checking after some expected time?? the while loop have specific expectations during installation. When those expectation do not ever match, the loop run for even.
• Validate xml before installation and exit then if problem appears

[0] http://aquarius.suse.cz/tests/11324