My app used to work ok with xulrunner 14. When I updated it with xulrunner 15,
it doesn't start up. The console shows the following messages:
com.app.launchd.peruser.501: ([0x0-0xabfabf].testapp[7866]): Exited with code:
255
Any idea what this is about? Anything config files (like info.plis
On 31/08/12 03:59 PM, Ehsan Akhgari wrote:
On 12-08-31 11:45 AM, Chris AtLee wrote:
On 31/08/12 11:32 AM, Ehsan Akhgari wrote:> There are extremely
non-stable Talos tests, and relatively stable ones.
> Let's focus on the relatively stable ones. There are extremely hard
> to diagnose perform
On 12-08-31 11:45 AM, Chris AtLee wrote:
On 31/08/12 11:32 AM, Ehsan Akhgari wrote:> There are extremely
non-stable Talos tests, and relatively stable ones.
> Let's focus on the relatively stable ones. There are extremely hard
> to diagnose performance regressions, and extremely easy ones (i
Hi,
Next Monday is a holiday here in Toronto. And we've had gfx meetings
each of the previous mondays. So, no meeting next week.
Benoit
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
There are a few issues here which should be easy to address and a few other
issues which are not so easy to address.
First off everybody who is interested in talos should read the wiki page:
https://wiki.mozilla.org/Buildbot/Talos
This explains where the code lives, what tests we run and on whic
On 31/08/12 11:32 AM, Ehsan Akhgari wrote:> There are extremely
non-stable Talos tests, and relatively stable ones.
> Let's focus on the relatively stable ones. There are extremely hard
> to diagnose performance regressions, and extremely easy ones (i.e.,
> let's not wait on this lock, do this
On 8/31/12 8:28 AM, Aryeh Gregor wrote:
In practice, I've noticed minimal difference using SSDs on my desktop,
which has 16G of RAM. I have lots of other stuff open, but all that
only uses a couple of gigs of RAM, so there should certainly be 9G for
page cache. (free -m reports about 7G used fo
> There are extremely non-stable Talos tests, and relatively stable ones.
> Let's focus on the relatively stable ones.
It's not exclusively a question of noise in the tests. Even
regressions in stable tests are sometimes hard to track down. I spent
two months trying to figure out why I could not
On 12-08-31 5:37 AM, Justin Lebar wrote:
Sorry to continue beating this horse, but I don't think it's quite dead yet:
One of the best things we could do to make finding these regressions
easier is to never coalesce Talos on mozilla-inbound. It's crazy to
waste developer time bisecting Talos loc
On 12-08-31 6:01 AM, Justin Lebar wrote:
I'm not saying it should be OK to regress our performance tests, as a
rule. But I think we need to acknowledge that hunting regressions can
be time-consuming, and that a policy requiring that all regressions be
understood may hamstring our ability to get
On 12-08-31 8:28 AM, Aryeh Gregor wrote:
If you use a desktop and work on compiled code even part-time, at any
reasonable pay rate, I can't see any reason why you wouldn't get 16G
of RAM. Although it seems most people don't -- maybe people mostly
use laptops? 2x8G of desktop RAM is about $75 ri
On Thu, Aug 30, 2012 at 1:25 AM, Gregory Szorc wrote:
> If you have 9+GB of memory dedicated to building mozilla-central and you are
> doing warm builds all the time, great, you probably don't need an SSD. But,
> those conditions are specialized. You have to get things into the page
> cache. That'
> IMHO we *can* regress on synthetic ones as long as we know what is going on.
It's the requirement that we know what is going on that I think is unreasonable.
Indeed, we /have/ a no not-understood regresisons policy, IIRC. The
extent to which it's being ignored is at least partially indicative
Sorry to continue beating this horse, but I don't think it's quite dead yet:
One of the best things we could do to make finding these regressions
easier is to never coalesce Talos on mozilla-inbound. It's crazy to
waste developer time bisecting Talos locally when we don't run it on
every push.
A
On Thursday, August 30, 2012 9:05:40 PM UTC-4, Ben Hearsum wrote:
> On 08/30/12 07:22 PM, L. David Baron wrote:
>
> > On Thursday 2012-08-30 14:42 -0700, Taras Glek wrote:
>
> >> * Joel will revisit maintaining Talos within mozilla-central to
>
> >> reduce developer barriers to understanding wha
15 matches
Mail list logo
