On 25/08/2014 7:41 PM, Erik Joelsson wrote:
On 2014-08-25 02:23, David Holmes wrote:
On 22/08/2014 1:39 AM, Erik Joelsson wrote:
Hello Aleksey,
As I have tried to explain a couple of times now: The jdk8 build built
each repository in sequence (much like the jdk7 build did). Because of
this it
On 2014-08-25 02:23, David Holmes wrote:
On 22/08/2014 1:39 AM, Erik Joelsson wrote:
Hello Aleksey,
As I have tried to explain a couple of times now: The jdk8 build built
each repository in sequence (much like the jdk7 build did). Because of
this it made sense to add messages about which repos
It would be nice to have a message indicating that a module build has
been completed as it would make a bit easier to figure out when a
failure occur.
On Mon, Aug 25, 2014 at 2:23 AM, David Holmes wrote:
> On 22/08/2014 1:39 AM, Erik Joelsson wrote:
>>
>> Hello Aleksey,
>>
>> As I have tried to e
On 22/08/2014 1:39 AM, Erik Joelsson wrote:
Hello Aleksey,
As I have tried to explain a couple of times now: The jdk8 build built
each repository in sequence (much like the jdk7 build did). Because of
this it made sense to add messages about which repository was being
built and measure the time
On Fri, Aug 22, 2014 at 3:10 AM, Erik Joelsson
wrote:
>
> On 2014-08-22 01:10, Martin Buchholz wrote:
>
> Serial execution is useful for both resource-constrained environments and
> for folks trying to profile the build itself. Serial build is also likely
> to be optimal if you are optimizing fo
Hi Erik,
Thanks for the explanations, comments below:
On 08/21/2014 07:39 PM, Erik Joelsson wrote:
> As I have tried to explain a couple of times now: The jdk8 build built
> each repository in sequence (much like the jdk7 build did). Because of
> this it made sense to add messages about which rep
On 2014-08-22 01:35, Jonathan Gibbons wrote:
I like the new finer grained parallelism in general (builds are
faster), but I do find the default output more confusing because it is
harder to see the warning messages go rushing past.
I agree that this is a problem. It can be partially mitigated
On 2014-08-22 01:10, Martin Buchholz wrote:
Serial execution is useful for both resource-constrained environments
and for folks trying to profile the build itself. Serial build is
also likely to be optimal if you are optimizing for total energy used
rather than total wall clock time.
If you
I like the new finer grained parallelism in general (builds are faster),
but I do find the default output more confusing because it is harder to
see the warning messages go rushing past.
Of course, a good solution would be to work on addressing the warnings
so that there are no warning message
Serial execution is useful for both resource-constrained environments and
for folks trying to profile the build itself. Serial build is also likely
to be optimal if you are optimizing for total energy used rather than total
wall clock time.
On Thu, Aug 21, 2014 at 8:39 AM, Erik Joelsson
wrote:
Hello Aleksey,
As I have tried to explain a couple of times now: The jdk8 build built
each repository in sequence (much like the jdk7 build did). Because of
this it made sense to add messages about which repository was being
built and measure the time each took. The new jdk9 build is not
repo
Hi,
The recent update of jdk9/jdk9 build scripts had significantly
deteriorated the usability of the build summary. This what was printed
before:
--- 8< -
Building OpenJDK for target 'default' in configuration
'linux-x86_64-normal-s
12 matches
Mail list logo
