[QA] browser tests race condition with login/logout

[Antoine Musso]

Le 01/07/2014 19:24, Jon Robson a écrit :
>> I guess whenever we logout, all that username sessions are invalidated
>> on the server side.
> 
> That is correct and apparently by design. [1]
> 
>>
>> The fix would be to use different username probably. Or have the per
>> user session invalidation to only invalidate the given session id and
>> not per username (havent looked at mediawiki core code).
> I think this would make sense. Is it possible to do this easily? e.g.
> have users such as selenium-mobile etc
> 
> [1] https://bugzilla.wikimedia.org/show_bug.cgi?id=49890

If it is indeed a race condition, we need only one job per target domain
(ie beta / prod).

Jenkins has a plugin that let job hold a lock and thus prevent other
jobs from running while the lock is held.  That might be a workaround
but would slowdown the build.

https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin

And JJB supports it:
http://ci.openstack.org/jenkins-job-builder/properties.html#properties.throttle


Examples of JJB definitions could be:

properties:
  - throttle:
      max-total: 1
      categories:
        - browsertests-beta

properties:
  - throttle:
      max-total: 1
      categories:
        - browsertests-prod



-- 
Antoine "hashar" Musso