On 23/09/2013 4:10 PM, Gregory Szorc wrote:
thread and to every armchair quarterback that shows up.
Really? :(
[I also see a clobber build spend > 5 minutes in various configure
runs, which frustrates me every time I see it - so I minimize the
shell ;]
We don't have much love for configure either. However, it's only
contributing a few extra minutes to Windows builds compared with 15+
minutes that pymake and make traversal is. I hope you understand why
fixing configure isn't at the top of the priority list at the
moment.
I understand it isn't at the top of the priority list, but it's still
worth keeping it in perspective - I see ~6 minutes of configure for ~30
mins total build time - 20% is significant in anyone's language.
~6 minutes for a configure?! I just did a configure from a clobber build
on Windows on my i7-2600K (2+ year old CPU) and it took 2:10. If you are
seeing 6 minutes configure times, you are running an ancient CPU and/or
not an SSD or you have something fubar with your setup (such as running
a VM inside a VM inside a VM Inception style). If your machine *is*
modern and you don't believe you are doing something silly, *please*
file a bug so we can get to the root cause.
I just did it again, and this time I saw 3 minutes 50 seconds from
"./mach build" until the first non-configure thing happened. It looks
like it ran configure 5 times, so might not be what you mean by "did a
configure".
I can't explain why I regularly saw > 5 minutes previously, but it's
still 10% of the build time. Should I open a bug on that?
[This is all on an i7-3770 CPU with 16GB ram on a spinning RAID disk in
a native (ie, non-VM) windows 7 - but a ~35 min build time implies it's
not particularly slow, right?]
Mark
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
