1) Yeah, feel free to pull me in on these conversations. I'm here to
help :)
2) What Robla said plus: Please feel free, actually, please feel
encouraged to report bugs on these specific infrastructure-failure tests
and assign to Chris or Zeljko and bring up in the SoS as appropriate.
Any infrastructure migration will be bumpy when there are some odd black
holes we need to debug. They'll debug/process them as fast as they can.
Greg
(PS: I trimmed cc's to just the lists, assuming all were on one of the
two)
<quote name="Rob Lanphier" date="2014-07-10" time="12:06:39
-0700">
Hi all,
Antoine and Zeljko are the right people to talk about this while Chris is
out, and it's late in the day for them. I'm sure they'll get back to you
tomorrow. Greg may be able to say more about this, but honestly, the
nature of this thread is a little bit like little kids in the backseat
saying "are we there yet? are we there yet?" repeatedly :-)
Antoine's response seems to answer the substance of what y'all are asking
about. We moved from Cloudbees to directly using Saucelabs so that we
could debug these issues directly. Now that we're on Saucelabs, we have
the info (see Antoine's mail). As he said, we have no plans to set up our
own version of Saucelabs.
It may be that the very first thing we need to do is put some sort of
environment health check prior to executing the actual test portion to
avoid these false failures. Given that the team just completed the
migration off of Cloudbees, give them a little time to figure things out.
Thanks
Rob
On Thu, Jul 10, 2014 at 11:09 AM, Tomasz Finc <tfinc(a)wikimedia.org> wrote:
> RobLa, is this something that we should be pulling in Greg for?
>
> --tomasz
>
> On Thu, Jul 10, 2014 at 11:08 AM, Arthur Richards
> <arichards(a)wikimedia.org> wrote:
> > Head's up that Chris Mcmahon is on vacation all this week. That said, it
> > would be great to hear from anyone in QA about this - it has been a long
> > standing issue.
> >
> >
> > On Thu, Jul 10, 2014 at 10:51 AM, Tomasz Finc <tfinc(a)wikimedia.org>
> wrote:
> >>
> >> ChrisMC,
> >>
> >> Are these failures unique to mobile? They seem look to be at the
> >> infrastructure level so i'm guessing it would affect others.
> >>
> >> What other information do you need from us to be able to remedy these?
> >>
> >> --tomasz
> >>
> >> On Wed, Jul 9, 2014 at 5:54 PM, Jon Robson <jdlrobson(a)gmail.com>
wrote:
> >> > Indeed. The tests have been failing for a month now, and had been
> >> > passing green before the move to
integration.wikimedia.org
> >> > It would be really good to get these back to being useful.
> >> >
> >> > I'm not sure how our interaction with saucelabs changed during
that
> >> > move, but is there anything that can be done on the short term to get
> >> > it back to how they were before when we were on cloudbees?
> >> >
> >> > Thanks Juliusz for the good summary of the problems!
> >> >
> >> >
> >> > On Wed, Jul 9, 2014 at 3:57 PM, Juliusz Gonera
<jgonera(a)wikimedia.org
> >
> >> > wrote:
> >> >> Today I worked a bit on fixing failing browser tests. The good
news
> is
> >> >> that
> >> >> some tests detected a regression in core that caused full text
search
> >> >> on
> >> >> mobile to not work. The bad news is that many of the failures seem
to
> >> >> be
> >> >> caused by problems with Saucelabs and/or beta labs, examples:
> >> >>
> >> >>
> >> >>
>
https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Mob…
> >> >> Editor doesn't seem to load, possible causes: beta labs API
error, or
> >> >> problem with connection between saucelabs and beta labs
> >> >>
> >> >>
> >> >>
>
https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Mob…
> >> >> getaddrinfo: Name or service not known (SocketError) - seems like
a
> >> >> problem
> >> >> with network on saucelabs
> >> >>
> >> >>
> >> >>
>
https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Mob…
> >> >> Saucelabs recording shows "no data received" error in
Chrome, either
> >> >> beta
> >> >> labs problem or saucelabs network problem
> >> >>
> >> >>
> >> >>
>
https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Mob…
> >> >> same as above
> >> >>
> >> >> Those are just a few examples from recent failures, but they make
> >> >> tracking
> >> >> regressions really tedious and time consuming. I know we are
planning
> >> >> to
> >> >> move away from Saucelabs and use our own servers to run the
tests.
> When
> >> >> will
> >> >> this happen? Is there any deadline?
> >> >>
> >> >> Thanks,
> >> >> --
> >> >> Juliusz
> >> >>
> >> >> _______________________________________________
> >> >> Mobile-l mailing list
> >> >> Mobile-l(a)lists.wikimedia.org
> >> >>
https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > Jon Robson
> >> > *
http://jonrobson.me.uk
> >> > *
https://www.facebook.com/jonrobson
> >> > * @rakugojon
> >> >
> >> > _______________________________________________
> >> > Mobile-l mailing list
> >> > Mobile-l(a)lists.wikimedia.org
> >> >
https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >
> >
> >
> >
> > --
> > Arthur Richards
> > Team Practices Lead
> > [[User:Awjrichards]]
> > IRC: awjr
> > +1-415-839-6885 x6687
>
_______________________________________________
Mobile-l mailing list
Mobile-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |