On 11/20/2013 08:11 AM, Tim Abraldes wrote:
Somebody stop me if this already exists...
I'm envisioning a central location, probably a wiki page at
https://wiki.mozilla.org/BrokenBuilds or similar, where people can find
the answers to these questions:
1. Given my current build configuration, w
> > Somebody stop me if this already exists...
> >
> > I'm envisioning a central location, probably a wiki page at
> > https://wiki.mozilla.org/BrokenBuilds or similar, where people can find
> > the answers to these questions:
> > 1. Given my current build configuration, why did my last build fai
> I like where you are coming from.
Yay!
> However, if we know what build bustage is known, it should be codified
> in the tree and the build should abort or you should see a giant
> warning. If we put this information anywhere else, I fear it will become
> out of date very quickly or filled with
On 11/18/13, 11:15 PM, Gregory Szorc wrote:
Do builds feel like they've gotten faster in the last few weeks^hours?
It's because they have.
When I did my MacBook Pro comparison [1] with a changeset from Oct 28,
build times on my 2013 2.6 GHz MacBook Pro were as follows:
Wall 11:13 (673)
User
On Tue, Nov 19, 2013 at 3:17 PM, Tim Abraldes wrote:
> Somebody stop me if this already exists...
>
> I'm envisioning a central location, probably a wiki page at
> https://wiki.mozilla.org/BrokenBuilds or similar, where people can find the
> answers to these questions:
> 1. Given my current bu
I like where you are coming from.
However, if we know what build bustage is known, it should be codified
in the tree and the build should abort or you should see a giant
warning. If we put this information anywhere else, I fear it will become
out of date very quickly or filled with content tha
Somebody stop me if this already exists...
I'm envisioning a central location, probably a wiki page at
https://wiki.mozilla.org/BrokenBuilds or similar, where people can find the
answers to these questions:
1. Given my current build configuration, why did my last build fail?
2. What bugs can
On Mon, Nov 18, 2013 at 11:15:16PM -0800, Gregory Szorc wrote:
> Do builds feel like they've gotten faster in the last few weeks^hours?
> It's because they have.
>
> When I did my MacBook Pro comparison [1] with a changeset from Oct 28,
> build times on my 2013 2.6 GHz MacBook Pro were as follows:
On Tue, Nov 19, 2013 at 6:36 AM, Benoit Jacob wrote:
>
> Because of the way it ended being used in many places, SurfaceDescriptor was
> involved in maybe half of the b2g 1.2 blocking (koi+) graphics crashes that
> we went over over the past few months.
>
> During the Paris work week we had extende
On 2013-11-19 12:16 PM, Neil wrote:
"ReferenceError: is is not defined".
This is coming from code like:
is(a, b, "message");
without the function `is' being defined.
Cheers,
Ehsan
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https:/
On 11/14/13, 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 that, the build syste
Hi All,
Due to the Dec 20-Jan 2 shutdown we're adjusting the release calendar to
accommodate the time off without losing time on development & quality assurance
for our 2014 releases. To that end, see
https://wiki.mozilla.org/RapidRelease/Calendar which has the updated release
schedule for Fi
On 11/19/2013 10:12 AM, nsm.nik...@gmail.com wrote:
Is there are reason devtools cannot switch to DOM Promises directly rather than
go through making Promise.jsm a wrapper around DOM Promise? The current promise
implementations which allow resolving later are leading to very un-idiomatic
promi
On Monday, November 18, 2013 5:36:48 PM UTC-8, Brandon Benvie wrote:
> On 11/18/2013 4:54 PM, Dave Townsend wrote:
>
> > There are add-ons using the existing promises implementations. Is there any
>
> > reason not to make those wrappers around the DOM promises to avoid
>
> > potential bustage?
>
On Monday, November 18, 2013 4:54:31 PM UTC-8, Dave Townsend wrote:
> There are add-ons using the existing promises implementations. Is there any
>
> reason not to make those wrappers around the DOM promises to avoid
>
> potential bustage?
>
>
>
> At least the add-on SDK promises library provi
On 19 November 2013 17:16:16, Neil wrote:
So I was quite surprised to find all manner of junk seems to get
reported to the console in a typical test run, including such goodies
as "ReferenceError: is is not defined".
Why does that not seem to cause a problem yet one particular exception
causes a
On 11/19/13 12:26 PM, Anne van Kesteren wrote:
On Tue, Nov 19, 2013 at 5:17 PM, Boris Zbarsky wrote:
It's been the case since late August, though the behavior is a bit
different: only thrown Errors or rejections with an Error are logged, not
arbitrary rejections.
Why are we doing it only for
On Tue, Nov 19, 2013 at 5:17 PM, Boris Zbarsky wrote:
> It's been the case since late August, though the behavior is a bit
> different: only thrown Errors or rejections with an Error are logged, not
> arbitrary rejections.
Why are we doing it only for Error objects?
--
http://annevankesteren.n
On 11/19/13 12:05 PM, David Rajchenbach-Teller wrote:
Generally, I believe that it's a good idea, if DOM Promises have the
equivalent of:
https://dutherenverseauborddelatable.wordpress.com/2013/10/14/recent-changes-to-promise-jsm-and-task-jsm/
Is this the case already?
It's been the case sinc
I was pinged because running the browser-chrome tests in chunks of three
makes a test that I reviewed fail by reporting an exception to the console.
So I was quite surprised to find all manner of junk seems to get
reported to the console in a typical test run, including such goodies as
"Refere
Generally, I believe that it's a good idea, if DOM Promises have the
equivalent of:
https://dutherenverseauborddelatable.wordpress.com/2013/10/14/recent-changes-to-promise-jsm-and-task-jsm/
Is this the case already?
Cheers,
David
On 11/19/13 1:38 AM, Nikhil Marathe wrote:
> (Cross posted to fi
We are adding a disable cache option to the developer tools because it would be
very useful for web and fxOS app devs.
Before we land it we would like to create a browser mochitest but we are
struggling to find a way to force caching of testfiles.html (obviously
necessary to test a disable cach
The current certificate for https://hg.mozilla.org will expire soon. The new
certificate will be installed on Thursday, Nov 21st at 0600PST(0900EST,
1400UTC). No interruption of service is expected, however anyone who has pinned
the current certificate fingerprint in their Mercurial rc file wil
2013/11/19 Nicholas Nethercote
> And the comment at https://bugzilla.mozilla.org/show_bug.cgi?id=915940#c13is
> worrying:
> "... once allocated the memory is only referenced via a SurfaceDescriptor,
> which is a generated class (from IPDL). These are then passed around from
> thread to thread and
Hi,
It feels to me like there have been quite a few graphics-related memory leaks
recently.
Here are a couple that have been fixed:
https://bugzilla.mozilla.org/show_bug.cgi?id=937878 (layer retention)
https://bugzilla.mozilla.org/show_bug.cgi?id=938612 (canvas leak)
Here is one that's still ope
(firefox-dev is a better venue for this question, redirecting there)
We don't currently have any active plans for "persistent tabs".
Pinned tabs should be difficult to accidentally close since Firefox 4
(bug 580638), though, so I wonder why they don't address your use
case.
Gavin
On Mon, Nov 18
26 matches
Mail list logo
