On Sun, Nov 17, 2013 at 2:17 AM, smaug wrote:
>
> the recent OOM cases have been really annoying. They have slowed down
> development, even for those who
> haven't been dealing with the actual issue(s).
>
> Could we handle this kind of cases differently. Perhaps clone the bad state
> of m-i to
> s
On Sat, Nov 16, 2013 at 4:34 AM, Ms2ger wrote:
> On 11/14/2013 11:49 PM, Ehsan Akhgari wrote:
>
>> I've started to work on a project in my spare time to switch us to use
>> unified builds for C/C++ compilation. The way that unified builds work is
>>
>> by using the UNIFIED_SOURCES instead of the
On Sat, Nov 16, 2013 at 5:26 AM, Gabriele Svelto wrote:
> On 14/11/2013 23:49, Ehsan Akhgari wrote:
>
>> The advantage of this is that it speeds up the compilation (I've measured
>> between 6-15x speed improvement depending on the code in question
>> locally.)
>>
>
> Another advantage would be tha
On Sat, Nov 16, 2013 at 10:34:38AM +0100, Ms2ger wrote:
> On 11/14/2013 11:49 PM, Ehsan Akhgari wrote:
> >I've started to work on a project in my spare time to switch us to use
> >unified builds for C/C++ compilation. The way that unified builds work is
> >by using the UNIFIED_SOURCES instead of t
On Thu, Nov 14, 2013 at 2:49 PM, Ehsan Akhgari wrote:
> I've started to work on a project in my spare time to switch us to use
> unified builds for C/C++ compilation. The way that unified builds work is
> by using the UNIFIED_SOURCES instead of the SOURCES variable in moz.build
> files. With tha
On Sunday 2013-11-17 16:45 -0800, Jonas Sicking wrote:
> On Thu, Nov 14, 2013 at 2:49 PM, Ehsan Akhgari
> wrote:
> > I've started to work on a project in my spare time to switch us to use
> > unified builds for C/C++ compilation. The way that unified builds work is
> > by using the UNIFIED_SOURC
On Sat, Nov 16, 2013 at 1:34 AM, Ms2ger wrote:
>
> One issue I only thought of today: this means that Source2.cpp can use all
> headers included into Source1.cpp–until enough files are added between
> Source1 and Source2 that Source2 ends up in the next unified file. This
> hasn't been much of an
Hi,
As you probably know, we just had a second (in a matter of weeks)
prolonged tree closure due to tests OOMing.
The post-mortem for the last tree closure
(https://etherpad.mozilla.org/mEB0H50ZjX) was quite satisfactory...
basically "we fixed some leaks, tweaked some silly tests, and know how
to
Here is a wiki page to track our progress on this front and our means of
synchronizing on this work:
https://wiki.mozilla.org/Platform/Porting_to_unified_sources
Benoit
2013/11/14 Ehsan Akhgari
> I've started to work on a project in my spare time to switch us to use
> unified builds for C/C++
I think we fixed this with:
http://hg.mozilla.org/mozilla-central/rev/49e797ce0f22
On Nov 14, 2013, at 9:34 AM, John Cook wrote:
> I'm trying to manually or programmatically set the geo.wifi.uri for
> testing purposes. I've tried to do this several different ways to no
> avail.I ma
Which would be in Firefox 27 http://aurora.mozilla.org for a download link.
Kevin Brosnan
On Sun, Nov 17, 2013 at 7:36 PM, Doug Turner wrote:
> I think we fixed this with:
> http://hg.mozilla.org/mozilla-central/rev/49e797ce0f22
>
>
>
> On Nov 14, 2013, at 9:34 AM, John Cook wrote:
>
> >
In particular, this should be fixed in Firefox 27 (currently on Aurora).
On 11/18/2013 11:36 AM, Doug Turner wrote:
I think we fixed this with:
http://hg.mozilla.org/mozilla-central/rev/49e797ce0f22
On Nov 14, 2013, at 9:34 AM, John Cook wrote:
I'm trying to manually or programmati
12 matches
Mail list logo
