On Wed, Aug 15, 2012 at 11:24:41PM -0700, Gregory Szorc wrote:
> On 8/15/12 11:10 PM, Mike Hommey wrote:
> >Something I noticed recently is that we spend more than 5 minutes (!)
> >during windows clobber builds to do the clobber (rm -rf). All try builds
> >are clobbers. A lot of time is wasted on m
On 8/15/12 11:10 PM, Mike Hommey wrote:
Something I noticed recently is that we spend more than 5 minutes (!)
during windows clobber builds to do the clobber (rm -rf). All try builds
are clobbers. A lot of time is wasted on mercurial cloning, too.
What is interesting is that the corresponding ti
On Wed, Aug 15, 2012 at 09:16:04PM -0400, Ehsan Akhgari wrote:
> On 12-08-15 6:17 PM, William Lachance wrote:
> >On 08/14/2012 03:47 PM, Gregory Szorc wrote:
> >>On 8/14/12 12:14 PM, Ed Morley wrote:
> >>>On Thursday, 9 August 2012 15:35:28 UTC+1, Justin Lebar wrote:
> Is there a plan to mitig
On 12-08-15 9:18 PM, Gregory Szorc wrote:
On 8/15/12 6:16 PM, Ehsan Akhgari wrote:
Honestly, the only big thing that we can probably fix to improve our
end-to-end times is to enable using pymake on our Windows builders to do
parallel builds. Developers on Windows have been using pymake to get
p
On 8/15/12 6:16 PM, Ehsan Akhgari wrote:
Honestly, the only big thing that we can probably fix to improve our
end-to-end times is to enable using pymake on our Windows builders to do
parallel builds. Developers on Windows have been using pymake to get
parallel builds for quite a while now, and s
On 12-08-15 6:17 PM, William Lachance wrote:
On 08/14/2012 03:47 PM, Gregory Szorc wrote:
On 8/14/12 12:14 PM, Ed Morley wrote:
On Thursday, 9 August 2012 15:35:28 UTC+1, Justin Lebar wrote:
Is there a plan to mitigate the coalescing on m-i? It seems like that
is a big part of the problem.
On 12-08-15 6:10 PM, Gregory Szorc wrote:
On 8/15/12 2:52 AM, Aryeh Gregor wrote:
On Tue, Aug 14, 2012 at 10:47 PM, Gregory Szorc wrote:
Is there a tracking bug for areas where we could gain efficiency? We all
know the build phase is full of clownshoes. But, I believe we also do
silly
things l
I have published an experimental patch for building mozilla-central
faster! Details are at [1].
If you are feeling brave, please give it a shot and report your
experiences. I am using this as part of my day-to-day development, so
you don't need to be too brave ;)
[1]
http://gregoryszorc.com
All the gory details in bug 773120 [1].
Cheers,
Chris
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=773120
Sorry, this should be https://bugzilla.mozilla.org/show_bug.cgi?id=775620
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https
On Wednesday, August 15, 2012 2:03:38 PM UTC-7, Taras Glek wrote:
> Hi,
>
> According to metrics we have about 1TB of telemetry data in hadoop. This
> is almost a year worth of telemetry data. Our telemetry ping packets
> keep growing as we add more probes. As the hadoop database gets bigger,
>
On 8/15/12 3:17 PM, William Lachance wrote:
In general I would be very careful before tackling any particular bug
for the sake of improving our build/test times. If something is slow,
but not on the critical path as far as build/test is concerned, fixing
it will not result in any tangible improve
On Tue, Aug 14, 2012 at 12:38 PM, Justin Lebar wrote:
>>> Is there a plan to mitigate the coalescing on m-i? It seems like that
>>> is a big part of the problem.
>>
>> it's simply a case of demand exceeding capacity.
>
> Understood.
>
> But I think my question still stands: Is there a plan to add
On 08/14/2012 03:47 PM, Gregory Szorc wrote:
On 8/14/12 12:14 PM, Ed Morley wrote:
On Thursday, 9 August 2012 15:35:28 UTC+1, Justin Lebar wrote:
Is there a plan to mitigate the coalescing on m-i? It seems like that
is a big part of the problem.
Reducing the amount of coalescing permitted w
On 8/15/12 2:52 AM, Aryeh Gregor wrote:
On Tue, Aug 14, 2012 at 10:47 PM, Gregory Szorc wrote:
Is there a tracking bug for areas where we could gain efficiency? We all
know the build phase is full of clownshoes. But, I believe we also do silly
things like execute some tests serially, only takin
On 08/15/12 12:41, Ben Hearsum wrote:
On 08/15/12 02:57 PM, Justin Wood (Callek) wrote:
XULRunner is currently an unsupported piece of software, we don't run
tests for it, and we *barely* ensure it still builds.
I don't think this is true. It's not tier1, but we ship it with every
release and
On 8/15/2012 2:42 PM, Benjamin Smedberg wrote:
On 8/15/2012 5:03 PM, Taras Glek wrote:
Hi,
According to metrics we have about 1TB of telemetry data in hadoop.
This is almost a year worth of telemetry data. Our telemetry ping
packets keep growing as we add more probes. As the hadoop database
gets
On 8/15/2012 5:03 PM, Taras Glek wrote:
Hi,
According to metrics we have about 1TB of telemetry data in hadoop.
This is almost a year worth of telemetry data. Our telemetry ping
packets keep growing as we add more probes. As the hadoop database
gets bigger, query times get worse, etc. We need
Hi,
According to metrics we have about 1TB of telemetry data in hadoop. This
is almost a year worth of telemetry data. Our telemetry ping packets
keep growing as we add more probes. As the hadoop database gets bigger,
query times get worse, etc. We need to decide on what data we can throw
away
Hi,
In the next day or so we're going to be changing the machines we're
using to do most of our fennec builds. This *should* be a no-op in terms
of functionality of the builds; we're using the same SDKs as before. The
new builds will be happening on slaves called 'bld-centos6-hp-XXX' or
'bld-
On 08/15/12 02:57 PM, Justin Wood (Callek) wrote:
> XULRunner is currently an unsupported piece of software, we don't run
> tests for it, and we *barely* ensure it still builds.
I don't think this is true. It's not tier1, but we ship it with every
release and beta. However, I'd be surprised if the
andreas.pals...@gmail.com wrote:
Hi.
I am curious if XUL Runner has an End-Of-Life policy?
Or is it intimately connected with Firefox, i.e. as long as there is Firefox
releases based on XUL there will be XUL Runner available too?
The reason I ask if because I am trying to "standardize" it with
Cross posting to dev-planning to ensure that the planning audience sees these
preliminary results.
Please post and responses to dev-platform.
- Original Message -
> The Layout, QA, and Market Insight teams recently analyzed the impact
> of aliasing Webkit CSS properties in Gecko with the
On Wednesday, 15 August 2012 13:46:59 UTC+12, pedb...@gmail.com wrote:
> Linus Torvalds flamed C++.
>
> - http://article.gmane.org/gmane.comp.version-control.git/57918
>
>
>
> Paul Graham said his company moved faster than its competition, because his
> company used Lisp.
>
> - http://www.pa
On 8/14/2012 9:46 PM, pedbe...@gmail.com wrote:
Linus Torvalds flamed C++.
- http://article.gmane.org/gmane.comp.version-control.git/57918
Paul Graham said his company moved faster than its competition, because his
company used Lisp.
- http://www.paulgraham.com/avg.html
Design Patterns are sol
On Tue, Aug 14, 2012 at 10:47 PM, Gregory Szorc wrote:
> Is there a tracking bug for areas where we could gain efficiency? We all
> know the build phase is full of clownshoes. But, I believe we also do silly
> things like execute some tests serially, only taking advantage of 1/N CPU
> cores in the
25 matches
Mail list logo