Hi,
With the increasing number of reports of local builds for Linux and
Android hitting the 32-bits address space limits when linking, and with
the fact that gcc 4.7 on try does hit that limit on PGO builds, it has
become necessary to switch the 32-bits Linux and Android builds to
64-bits
On 5/14/13 8:35 PM, Felipe Gomes wrote:
Should profile-before-change then be my call to stop accepting changes to the
data and call writeAtomic to flush it? I've seen some code nearby doing it at
quit-application-granted. Or perhaps there's no correct answer and it
varies case by case (or
On 5/15/13 2:42 AM, Mike Hommey wrote:
Following this, we're going to switch all Linux builds to gcc 4.7, later
this week.
Android NDK r8e also includes gcc 4.7. We may want to investigate
updating to gcc 4.7 on Android, too.
chris
___
On Wed, May 15, 2013 at 11:36:01AM -0700, Chris Peterson wrote:
On 5/15/13 2:42 AM, Mike Hommey wrote:
Following this, we're going to switch all Linux builds to gcc 4.7, later
this week.
Android NDK r8e also includes gcc 4.7. We may want to investigate
updating to gcc 4.7 on Android, too.
These jobs are now running across the board up to mozilla-aurora.
It seems that dromaeo css on pgo is misbehaving:
https://bugzilla.mozilla.org/show_bug.cgi?id=870453
cheers,
Armen
On 2013-05-13 11:23 AM, Armen Zambrano G. wrote:
The intermittent failures on consecutive changesets were not as
On 5/15/13 2:18 PM, Vladan Djeric wrote:
Hi all,
I recently came across a situation where it would have been useful to
control the order in which components receive the same shutdown
notification. Specifically, Telemetry writes out session data to the
profile dir during the
On 2013-05-15 5:18 PM, Vladan Djeric wrote:
I'd like to know if these use-cases are sufficiently rare that we should
just add new shutdown events when needed (e.g. we added
profile-before-change2 for Telemetry in bug 844331), or if we should
come up with a general way to impose order of shutdown
On Wed, May 15, 2013 at 05:18:09PM -0400, Vladan Djeric wrote:
Hi all,
I recently came across a situation where it would have been useful
to control the order in which components receive the same shutdown
notification. Specifically, Telemetry writes out session data to the
profile dir
I believe roc proposed just having an explicit hard coded list of things
to start up a while ago, and I'm tempted to say that's what we should do for
shutdown too. So just add an explicit call to some os.file thing
followd by a call to a telemetry function after profile-before-change
but not
On Wednesday 2013-05-15 14:32 -0700, Gregory Szorc wrote:
I think the more compelling use case is service startup. Proper
dependencies should allow us to more intelligently start services on
demand. This should lead to lower resource utilization and faster
startup times. Shutdown times should
On 5/15/13 3:31 PM, L. David Baron wrote:
On Wednesday 2013-05-15 14:32 -0700, Gregory Szorc wrote:
I think the more compelling use case is service startup. Proper
dependencies should allow us to more intelligently start services on
demand. This should lead to lower resource utilization and
Gregory Szorc wrote:
Ahh, I was thinking more of JS services. In this world, your manifest
adds an entry to the app-startup category and your service receives
the app-startup notification. It is customary for it to register an
observer for a later startup phase and finish initialization then.
On Wed, May 15, 2013 at 4:00 PM, Gregory Szorc g...@mozilla.com wrote:
Ahh, I was thinking more of JS services. In this world, your manifest adds
an entry to the app-startup category and your service receives the
app-startup notification. It is customary for it to register an observer
for a
Felipe Gomes schrieb:
What prompted the question is that I'm working on a conversion from SQLite
storage to a JSON file. OS.File.writeAtomic provides a good guarantee of data
consistency against crashes etc, and I'm now looking how to guarantee a proper
full flush of the data to disk during
David Rajchenbach-Teller schrieb:
I'd even go as far as limiting it to 16kb.
(possibly with a transition phase during which going above 16kb only
prints warnings)
I think most of us agree, but the problem is that apparently a number of
add-ons rely on large prefs atm, so right now we did set
15 matches
Mail list logo
