Thanks to Željko, the next emails we receive for build status should be significantly more useful.
Also, we had an instance of a Jenkins build marked red where no tests failed. We have an open ticket with Cloudbees for this and we will be working with them to find out why. https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs....
On Thu, Jan 9, 2014 at 5:00 AM, mobile-l-request@lists.wikimedia.orgwrote:
Send Mobile-l mailing list submissions to mobile-l@lists.wikimedia.org
To subscribe or unsubscribe via the World Wide Web, visit https://lists.wikimedia.org/mailman/listinfo/mobile-l or, via email, send a message with subject or body 'help' to mobile-l-request@lists.wikimedia.org
You can reach the person managing the list at mobile-l-owner@lists.wikimedia.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of Mobile-l digest..."
Today's Topics:
- Re: Build failed in Jenkins: MobileFrontend-en.m.wikipedia.org-linux-firefox #210 (Željko Filipin)
Message: 1 Date: Wed, 8 Jan 2014 16:13:33 +0100 From: Željko Filipin zfilipin@wikimedia.org To: Arthur Richards arichards@wikimedia.org Cc: mobile-l mobile-l@lists.wikimedia.org, mobile-tech mobile-tech@wikimedia.org, Chris McMahon < cmcmahon@wikimedia.org> Subject: Re: [WikimediaMobile] Build failed in Jenkins: MobileFrontend-en.m.wikipedia.org-linux-firefox #210 Message-ID: <CABfBeArvfjHiL7GADPf6vOnnuAv9GurCNePgxSiSeEYj9g8= Fw@mail.gmail.com> Content-Type: text/plain; charset="utf-8"
On Sat, Dec 21, 2013 at 6:31 PM, Željko Filipin <zfilipin@wikimedia.org
wrote:
I have talked with Chris about this and as far as he remember, the last time this happened we said we will contact Cloudbees support if it
happens
again. Since it happened again, I have now contacted support. I will let you know as soon as they reply.
Cloudbees support suggested to add --backtrack to cucumber[1]. Let's see if it helps.
Željko
On Thu, Jan 9, 2014 at 6:05 PM, Chris McMahon cmcmahon@wikimedia.orgwrote:
Thanks to Željko, the next emails we receive for build status should be significantly more useful.
Geoffrey Mon (one of the Google Code-in students) did all the work. I have sent screenshots to QA mailing list, I am attaching them here too.
Feel free to send thank you notes here, I will forward them to Geoffrey. If you would like to see something added/removed/changed, let us know.
Also, we had an instance of a Jenkins build marked red where no tests failed. We have an open ticket with Cloudbees for this and we will be working with them to find out why. https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs....
A few days ago I have added --backtrace option to Cucumber, since Cloudbees support has recommended it. Looks like it did not provide more information. I have contacted them again. I will let you know as soon as they reply.
Željko
On Fri, Jan 10, 2014 at 11:03 AM, Željko Filipin zfilipin@wikimedia.orgwrote:
A few days ago I have added --backtrace option to Cucumber, since Cloudbees support has recommended it. Looks like it did not provide more information. I have contacted them again. I will let you know as soon as they reply.
Cloudbees support had another idea[1], I have implemented it, but it did not help. I will let you know as soon as we make any progress.
If anybody has ideas on how to debug this, please do let me know.
Željko -- 1: https://gerrit.wikimedia.org/r/#/c/107164/
On Tue, Jan 14, 2014 at 1:50 PM, Željko Filipin zfilipin@wikimedia.orgwrote:
If anybody has ideas on how to debug this, please do let me know.
I am tracking this as bug #60037[1].
Željko -- 1: https://bugzilla.wikimedia.org/show_bug.cgi?id=60037
On Tue, Jan 14, 2014 at 1:50 PM, Željko Filipin zfilipin@wikimedia.orgwrote:
No e-mail notifications were sent for failed builds since this was implemented. When a test failed, instead of marking a job as failed, it marked it as unstable. We are now sending e-mail notifications for both unstable and failed jobs[2].
Željko -- 2: https://gerrit.wikimedia.org/r/#/c/107363/
