Added by okurz almost 7 years ago. Updated over 6 years ago.
0%
Description
same problem now in https://openqa.suse.de/tests/1235702#step/textinfo/6 in the curl URL. Compare the two URLs in the two subsequent curl calls. In the second one there is a doubled "h" which therefore resolves to an invalid URL.
VNC_TYPING_LIMIT already set to 10 for this job. It is a known issue in OpenQA api. When new build with aarch64 architecture will be available I will be able to retrigger the job lowering VNC_TYPING_LIMIT to 7.
Cannot see this failure anymore, not even in sle12sp4, at least in the mentioned job.
To my understanding aarch64 should not behave different than x86_64 therefore no special VNC_TYPING_LIMIT should be applied unless we know a specific problem which should then be handled in os-autoinst. I suggest the following:
VNC_TYPING_LIMIT= (unset) and check if there are any failuresTo trigger many jobs an example:
for i in {1..100}; do openqa-clone-job --skip-chained-deps --from https://openqa.suse.de --host https://openqa.suse.de --skip-download 1356341 VNC_TYPING_LIMIT= TEST=test_poo19438_jeriveramoya_$i _GROUP="Test Development: SLE 15" BUILD=XXX@test_poo19438 ; done
that did not seem to work. Some incompletes. Looks like the ISO can not be found in the pool directory. Maybe the original job does not have the ISO as well anymore? You could select a SLE15 corresponding job if that one has the ISO still.
I realized that the sample code was cloning a sle12sp4 job in sle15 development group so I edited the link (while you were writing probably :))
I used sle12 sp4 that is where the error was found originally. No incomplete atm: https://openqa.suse.de/tests/overview?version=12-SP4&groupid=132&build=XXX%40test_poo19438&distri=sle
It looks good except for some incomplete and one failure tests, but not related with typing. Removed setting VNC_TYPING_LIMIT for aarch64 in Machines configuration in OSD.