I tried to build m-c today with clang 5.0 and icecream using the following
mozconfig:
```
mk_add_options MOZ_MAKE_FLAGS="-j$(icecc-jobs)"
mk_add_options 'export CCACHE_PREFIX=icecc'
mk_add_options "export RUSTC_WRAPPER=sccache"
export CC=clang
export CXX=clang++
ac_add_options --with-ccache
This thread has gone way off the rails. Can you please take it
somewhere else? It's pretty wildly off topic for this list at
this point.
Thanks.
On Mon, Nov 06, 2017 at 04:56:18PM -0800, Jeff Gilbert wrote:
My understanding of current policy is that ECC is not required. (and
not even an optio
My understanding of current policy is that ECC is not required. (and
not even an option with MacBook Pros) Given the volume of development
that happens unhindered on our developers' many, many non-ECC
machines, I believe the burden of proof-of-burden is on the pro-ECC
argument to show that it's lik
On 06/11/2017 22:44, Jeff Gilbert wrote:
> Price matters, since every dollar we spend chasing ECC would be a
> dollar we can't allocate towards perf improvements, hardware refresh
> rate, or simply more machines for any build clusters we may want.
And every day our developers or IT staff waste cha
On 06/11/2017 18:46, Justin Wood wrote:
Now with Taskcluster the start time is anchored in UTC so doesn't move
along with Daylight Savings, currently anchoring at 10am and 10pm UTC.
Is that connected to merge times? Should the merges into M-C be done
just before those two times?
Right now it
Price matters, since every dollar we spend chasing ECC would be a
dollar we can't allocate towards perf improvements, hardware refresh
rate, or simply more machines for any build clusters we may want.
The paper linked above addresses massive compute clusters, which seems
to have limited implicatio
I haven't posted in a while, but I wanted to let everyone know what is new with
Talos and Performance Sheriffing.
I have a few blog posts outlining more details- in total we have 1127 different
perf metrics we track per commit and for Firefox 55, 56, and 57 >=50
regressions files/release [1]
M
On 2017-11-06 9:46 AM, Justin Wood wrote:
Now with Taskcluster the start time is anchored in UTC so doesn't move
along with Daylight Savings, currently anchoring at 10am and 10pm UTC.
How long do the Nightly builds typically take? If the builds are started
at 10am and 10pm UTC (2am and 5pm PST
Hey Everyone,
I was alerted to a confusion about when Nightlies Start since the US
Daylight Savings change this past weekend.
Previously [on buildbot] Nightlies would start at 3am Pacific Time.
Now with Taskcluster the start time is anchored in UTC so doesn't move
along with Daylight Savings, cu
> On Nov 6, 2017, at 05:19, Gabriele Svelto wrote:
>
>> On 04/11/2017 01:10, Jeff Gilbert wrote:
>> Clock speed and core count matter much more than ECC. I wouldn't chase
>> ECC support for general dev machines.
>
> The Xeon-W SKUs I posted in the previous thread all had identical or
> higher
On Mon, Nov 6, 2017 at 1:53 AM, David Teller wrote:
> I wanted to add something like that to about:performance, but at the
> time, my impression was that we did not have sufficient platform data on
> where allocations come from to provide something convincing.
>
The SpiderMonkey Debugger API ha
> Does this API avoid the problems described in
https://groups.google.com/forum/#!topic/mozilla.dev.platform/45XApRxACaM ?
Which specific issues?
The API in the specification is promise ready by using the permissions API,
is behind a permission prompt and requires a secure context.
My understandi
I second Kris on the fact that the main reason I go to #developer is because
of the reviewer / author ping that I get.
I am still looking into patches which are submitted when I am mentioned as a
reviewer, in case someone is pushing code without applying nits, or with
additional un-reviewed mo
I use #developers for two things:
1. I prefer to keep my discussions in smaller topic channels, but for my
sanity I also try to keep my channel list small. There is a large set of
people whom I ping roughly once a month and can't be bothered matching
channels with. #developers is my "lowest common
On 04/11/2017 01:10, Jeff Gilbert wrote:
> Clock speed and core count matter much more than ECC. I wouldn't chase
> ECC support for general dev machines.
The Xeon-W SKUs I posted in the previous thread all had identical or
higher clock speeds than equivalent Core i9 SKUs and ECC support with
the s
On 06/11/2017 12:49, Philipp Kewisch wrote:
If there is a better place to ask ad-hoc questions about Gecko, I am
happy to go there (and we should make sure the channel is promoted in
our docs).
I think different teams have ended up with different IRC channels, as
Kris said. Frontend Firefox st
On 11/5/17 12:55 PM, Mike Hommey wrote:
> So it seems to me the core problem is not as much "there's too much noise"
> as "people are not posting on #developers anymore". One could think
> there's correlation, but I think the reality is simply that less people
> use irc.
Thanks for the stats and h
As a user, I would definitely love to have this.
I wanted to add something like that to about:performance, but at the
time, my impression was that we did not have sufficient platform data on
where allocations come from to provide something convincing.
Cheers,
David
On 02/11/17 15:34, Randell Je
Hi everyone,
Here's the list of new issues found and filed by the Desktop Release QA
Team last week, *October 30 - November 3* (week 44).
Additional details on the team's priorities last week, as well as the
plans for the current week are available at:
https://public.etherpad-mozilla.org
Hi,
As the owner of the mentioned bot, I feel I need to jump in, not because
I want to defend any position (I pretty much don't care whether pulsebot
sends its messages to #developers or somewhere else), but just to
mention some facts.
Pulsebot did its first post to #developers on May 30, 2014, b
On 06/11/2017 00:23, zbranie...@mozilla.com wrote:
but please, be careful because #developers is also the most natural channel for
any newcomers to go to in order to ask entry level questions about our codebase.
No, that should be (and is and has been for a considerable amount of
time, IME),
Thank you for including an AMD card among the ones to be tested.
- -
The Radeon RX 460 mentioned earlier in this thread arrived. There was
again enough weirdness that I think it's worth sharing in case it
saves time for someone else:
Initially, for multiple rounds of booting with different cable
22 matches
Mail list logo