action #41408
closedWrong screenshots order
0%
Description
The screenshots order seems inverted here: https://openqa.suse.de/tests/2078133#step/yast2_nfs_server/6, if you look at the video, you can notice that the https://openqa.suse.de/tests/2078133#step/yast2_nfs_server/7 should be previous to that one.
Updated by coolo about 6 years ago
The clock on this machine seems to be really freaky. I just moved the ntp time 3 minutes forward.
{
"frametime" : [
"263.83",
"263.88"
],
"screenshot" : "yast2_nfs_server-6.png",
"result" : "unk",
"needles" : []
},
{
"text" : "yast2_nfs_server-7.txt",
"title" : "wait_serial",
"result" : "ok",
"needles" : []
},
{
"frametime" : [
"266.46",
"266.50"
],
"screenshot" : "yast2_nfs_server-9.png",
"result" : "unk",
"needles" : []
},
{
"frametime" : [
"264.33",
"264.38"
],
"tags" : [
"nfs-config",
"nfs-firewall",
"nfs-server-not-installed"
],
Updated by EDiGiacinto about 6 years ago
Seems the same happened also here: https://openqa.suse.de/tests/2110930#step/yast2_nfs_server/6
Updated by mloviska about 6 years ago
Another occurrence on the same worker sle-15-SP1-Installer-DVD-aarch64-Build58.3-cryptlvm@aarch64
Updated by okurz over 4 years ago
- Status changed from New to Resolved
- Assignee set to okurz
so this just shows that a proper clock on all machines is necessary :) The least we can do is mention the importance of synchronized clocks in docs: https://github.com/os-autoinst/openQA/pull/2891 :)
Since then we also improved the log output in case of timestamps that differ too much.