Overview
The SR for openQA is automatically created after the openQA-in-openQA job passed which is triggered after devel:openQA built successfully and a jenkins job triggers the copy to devel:openQA:tested. All this is not atomic so for example it could be that a rebuild is triggered after that or something like this. Not exactly sure what happened today or in which order
Ok, i see the difference between :tested and :openQA: in the nin-tested projet, you have a perl selenium driver package, which does not exist in ttpested; there, the one from openSUSE:Factory is bejng used, which in turn is version 1.23, and nit, as requested by openqa (why?) < 1.21
Request History
okurz created request
Update to 4.5.1517920216.2250682a
licensedigger accepted review
ok
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto added repo-checker as a reviewer
Please review build success
factory-auto accepted review
Check script succeeded
dimstar accepted review
staging-bot added openSUSE:Factory:Staging:adi:34 as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:34"
staging-bot accepted review
Picked openSUSE:Factory:Staging:adi:34
repo-checker accepted review
cycle and install check passed
staging-bot accepted review
ready to accept
staging-bot approved review
ready to accept
dimstar_suse accepted request
Accept to openSUSE:Factory
