Re: android-build's are failing, we're on it...
Hello, On Fri, 11 May 2012 11:09:59 +0200 Loïc Minier wrote: > * IRC is nice for this kind of announcements; you can even put it in >the #linaro topic > > * perhaps we can just add a banner to android-build.linaro.org? > > * perhaps a Linaro services dashboard is what we miss? e.g. "Android >build system: working" (green), or "broken (see LP #1234)"; Joey is >running a basic HTTP status monitor as part of Linaro IS Well, lack of context is indeed very bad thing. There was no known outages to Android Build as a service. So, my understanding is that Zack meant that for that particular day, there were lot of build failures, which is true, I looked at them too, identified something we can improve on Infra side (https://bugs.launchpad.net/linaro-android-infrastructure/+bug/997551), the rest where genuine compile errors. For those errors, https://android-build.linaro.org/ is *the dashboard*. Ah, as it's confession time, some time ago that page was prefixed with content, not really related to the Build System function, which exactly complicates access to build dashboard (requires lot of vertical scrolling). IMHO, that text is misplaced there - it belongs to releases.linaro.org/snapshot.linaro.org, which are gateways for community access, and android-build.linaro.org is first of all internal build system. Having extra stuff there complicates access and maintenance. > * notifications about build system going down could go to the same >places where build failures / successful builds are reported; > perhaps we need a dedicated "build-notifications" list or something > like that -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: android-build's are failing, we're on it...
* IRC is nice for this kind of announcements; you can even put it in the #linaro topic * perhaps we can just add a banner to android-build.linaro.org? * perhaps a Linaro services dashboard is what we miss? e.g. "Android build system: working" (green), or "broken (see LP #1234)"; Joey is running a basic HTTP status monitor as part of Linaro IS * notifications about build system going down could go to the same places where build failures / successful builds are reported; perhaps we need a dedicated "build-notifications" list or something like that -- Loïc Minier ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: android-build's are failing, we're on it...
On Fri, May 11, 2012 at 12:21 AM, Ricardo Salveti wrote: > On Thu, May 10, 2012 at 1:20 PM, Christian Robottom Reis > wrote: >> On Thu, May 10, 2012 at 12:55:26PM -0700, Ricardo Salveti wrote: >>> Sorry to say that, but I hate these kind of emails at Linaro Dev, as I >>> believe we have other places (and better ones) to report such issues. >>> Twitter would probably be the way to go. >> >> Well, to be honest I don't really see the problem with letting the list >> know that there are issues, and I interpret Zach's brevity as "we're >> totally focused on getting the problem solved". I expect he's going to >> come back and explain what's broken when the issue is resolved. > > Well, just saying it's broken doesn't help much either. If you really > want a better and more up-to-date place to show this info even IRC > would be better. > >> Is Twitter really that much better to inform us it's broken? I would >> have missed the news entirely, for one random data point. > > Better than email at least :-) While it it's useful, did it actually > help you in any front? > > Twitter is the general place used by most of projects for status > update, that's why I thought that it'd be the best way to go. > I would have preferred to get a bit more context as well, but as kiko said, getting an notification is definitely better than nothing. Especially if you are in the mids of a firedrill you might not have the time to explain the context, nor might you understand whats going on at all etc. -- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: android-build's are failing, we're on it...
On Thu, May 10, 2012 at 1:20 PM, Christian Robottom Reis wrote: > On Thu, May 10, 2012 at 12:55:26PM -0700, Ricardo Salveti wrote: >> Sorry to say that, but I hate these kind of emails at Linaro Dev, as I >> believe we have other places (and better ones) to report such issues. >> Twitter would probably be the way to go. > > Well, to be honest I don't really see the problem with letting the list > know that there are issues, and I interpret Zach's brevity as "we're > totally focused on getting the problem solved". I expect he's going to > come back and explain what's broken when the issue is resolved. Well, just saying it's broken doesn't help much either. If you really want a better and more up-to-date place to show this info even IRC would be better. > Is Twitter really that much better to inform us it's broken? I would > have missed the news entirely, for one random data point. Better than email at least :-) While it it's useful, did it actually help you in any front? Twitter is the general place used by most of projects for status update, that's why I thought that it'd be the best way to go. Cheers, -- Ricardo Salveti de Araujo ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: android-build's are failing, we're on it...
On 10 May 2012 15:20, Christian Robottom Reis wrote: > On Thu, May 10, 2012 at 12:55:26PM -0700, Ricardo Salveti wrote: >> Sorry to say that, but I hate these kind of emails at Linaro Dev, as I >> believe we have other places (and better ones) to report such issues. >> Twitter would probably be the way to go. > > Well, to be honest I don't really see the problem with letting the list > know that there are issues, and I interpret Zach's brevity as "we're > totally focused on getting the problem solved". I expect he's going to > come back and explain what's broken when the issue is resolved. Thanks Kiko. Yes, we sorted the issue out and we're back up. The builds are currently in flight. > Is Twitter really that much better to inform us it's broken? I would > have missed the news entirely, for one random data point. > -- > Christian Robottom Reis, Engineering VP > Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935 > Linaro.org: Open Source Software for ARM SoCs -- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: android-build's are failing, we're on it...
On Thu, May 10, 2012 at 12:55:26PM -0700, Ricardo Salveti wrote: > Sorry to say that, but I hate these kind of emails at Linaro Dev, as I > believe we have other places (and better ones) to report such issues. > Twitter would probably be the way to go. Well, to be honest I don't really see the problem with letting the list know that there are issues, and I interpret Zach's brevity as "we're totally focused on getting the problem solved". I expect he's going to come back and explain what's broken when the issue is resolved. Is Twitter really that much better to inform us it's broken? I would have missed the news entirely, for one random data point. -- Christian Robottom Reis, Engineering VP Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935 Linaro.org: Open Source Software for ARM SoCs ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: android-build's are failing, we're on it...
Sorry to say that, but I hate these kind of emails at Linaro Dev, as I believe we have other places (and better ones) to report such issues. Twitter would probably be the way to go. If you really need to send it to linaro-dev, would you mind at least giving more information and writing the email properly to avoid just using the subject? Thanks. -- Ricardo Salveti de Araujo ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
