On 4/22/16 2:25 PM, Gregory Szorc wrote:
There's a "Tools (1.3.1 and Windows 10 SDK
(10.0.10586)" update under "Windows and Web Development" -> "Universal
Windows App Development Tools" *that was released after VS2015 Update 2 was
initially released*.
Bug 1259782 if anyone has problems.
In co
On 5/9/14, 10:24 AM, Rik Cabanier wrote:
Out of interest, do you have links to bugs for this issue?
SpiderMonkey has one here:
https://bugzilla.mozilla.org/show_bug.cgi?id=948321
(Differential Testing: Different division results on x86 platforms)
and further differential testing on Win32 is b
On 5/29/13 9:05 PM, Brad Lassey wrote:
On 5/29/13 11:42 PM, Anthony Jones wrote:
What is the attendance like from the Asia-Pacific region?
I can't recall anyone from Asia-Pacific who is a regular attendee.
It is extremely difficult to (expect anyone to, or otherwise) regularly
attend a mee
Another potential problem with this approach is that we will have more
merge changes in m-c, which generally screws with hg bisect. Personally
I already have enough trouble with hg bisect to the point where I don't
use it because I can't trust it. This may be a legitimate problem for
some, but it'
As much as I'm a fan of Clang, a concern with switching builders from
GCC to Clang is losing continuous integration coverage of GCC. I believe
we considered this unacceptable when it was discussed a few months ago.
However, if Clang is better for our users and/or our automation, we can
reopen that
There should be very few warnings within the current Spidermonkey. I
suspect you may not be compiling with --enable-valgrind. This is
necessary because Spidermonkey uses a conservative garbage collector
that intentionally accesses lots of uninitialized memory, and
--enable-valgrind turns on direct
Running with --track-origins=yes should help with debugging this problem.
-Gary
>
> Below are some lines from memcheck session log of running TB under it.
>
> The number of such usages recorded in one session log is
>
> 68 Memcheck:Cond
>
> Close to 60 of them are related to Ja
Thinking of making the top level goals bugs and hanging related work off
them as deps. What do people think of this idea? Is it maintainable?
Sounds reasonable, they could be meta bugs, marked with the "meta" keyword.
-Gary
___
dev-platform mailing
On 12/24/12 11:36 AM, Rafael Ávila de Espíndola wrote:
I have been tracking the 3.2 branch for the clang packages we use on the bots
and have just push to m-i a change to use the 3.2 release.
This should hopefully make things easier for those building mozilla on OS X.
Maybe I'm missing someth
I filed bug 800471 for considering using Clang on Linux.
-Gary
This also suggests another option: using clang on linux too. This would
have the added benefit of using the same compiler for OS X and Linux,
which would remove most of the argument of developers spending time on
linux only issues.
I think we should have this data feed into a cronjob that emails the
top ~5 weekly (ab)users of try, notifies them of their impact, and
suggests ways the can help avoid using these resources unnecessarily.
Gavin
I agree with Gavin, the top users ought to be educated. Currently the
top folks (
Take a look at http://people.mozilla.org/~catlee/try_pushers.html. This
is a report of people who pushed to try within 60 minutes of their
previous push since September 1. In some cases patches are clearly
unrelated, and in other cases people have cancelled their previous job
(woohoo!). There are
Win7 x64 / i7@3.9GHz / 8 cores / 12GB@1600MHz / SSD mirrored, warm
clobbered build of debug desktop browser:
-j12: 19m00s exactly
-j9: 18m45s exactly
Using more processes then cores is counter productive. I checked
this 2 years ago already when build took just 13 minutes (we
grow!!).
Conclusio
I care about testing Firefox under valgrind, but if the valgrind builds are
red and have been red for a long time there's no point in continuing to run
them to see that they're still red.
They've been red for a long time partially because the Valgrind version
wasn't upgraded as Firefox was deve
MozillaBuild is currently shipping with 2.7.2. Lately, I've been
planning to update a few things in there, though, and upgrading it to
2.7.3 is on my list.
A few days ago, I filed bug 788911 for MozillaBuild to upgrade to 2.7.3.
-Gary
___
dev-platform
MozillaBuild is currently shipping with 2.7.2. Lately, I've been
planning to update a few things in there, though, and upgrading it to
2.7.3 is on my list.
A few days ago, I filed bug 788911 for MozillaBuild to upgrade to 2.7.3.
-Gary
___
dev-platform
So, 2.6 or 2.7?
Ideally 2.7. Releng also prefers python to be identical across build
machines, and new build machines are having some flavor of Python 2.7
installed (ref bug 602908).
See https://bugzilla.mozilla.org/show_bug.cgi?id=602908#c16
-Gary
__
17 matches
Mail list logo
