We just pushed some new UI elements from beta to stable which has now hit
beta labs. These haven't propagated to test2 or enwiki yet so these tests
are now failing.
How best should we do prevent these failures from recording while these
servers haven't been updated?
Is there anyway browser tests can be clever and run themselves based on the
current commit on master of the server they are hitting?
On Thu, Jan 23, 2014 at 1:36 PM, <jenkins-no-reply(a)cloudbees.com> wrote: