On 24 September 2012 10:44, Andrew Stubbs a...@codesourcery.com wrote:
On 22/09/12 13:13, Joel Rosdahl wrote:
I would be OK with caching failures if it's off by default and doesn't
affect the default's performance. Have you thought about how to store
the exit code in the cache?
The simplest
On 04/10/12 01:50, Shentino wrote:
Would snooping on the compiler's own error messages help weed out
transient failures like out of memory, disk full, and so on?
I recently compiled webkit-gtk and it managed to exhaust all of my
memory AND swap.
This does raise an interesting choice!
On the
On Fri, Oct 5, 2012 at 2:17 AM, Andrew Stubbs a...@codesourcery.com wrote:
On 04/10/12 01:50, Shentino wrote:
Would snooping on the compiler's own error messages help weed out
transient failures like out of memory, disk full, and so on?
I recently compiled webkit-gtk and it managed to
On Sat, Sep 29, 2012 at 6:23 PM, Martin Pool m...@sourcefrog.net wrote:
I think caching errors would be worth trying. It may help with
configure, and it may also help with people rebuilding trees that from
time to time have errors in them.
Depending on the compiler, it may be possible to see
On Mon, Sep 24, 2012 at 1:44 AM, Andrew Stubbs a...@codesourcery.com wrote:
On 22/09/12 13:13, Joel Rosdahl wrote:
On 18 September 2012 14:16, Andrew Stubbs a...@codesourcery.com wrote:
I'm aware that there's some danger here that we can end up caching Ctrl-C
interrupts, SIGTERM/SIGKILL
I think caching errors would be worth trying. It may help with
configure, and it may also help with people rebuilding trees that from
time to time have errors in them.
Depending on the compiler, it may be possible to see from the
waitstatus that it was interrupted, and so to avoid caching the
On 22/09/12 13:13, Joel Rosdahl wrote:
On 18 September 2012 14:16, Andrew Stubbs a...@codesourcery.com wrote:
I'm aware that there's some danger here that we can end up caching Ctrl-C
interrupts, SIGTERM/SIGKILL terminations, out-of-memory failures, and all
manner of other non-reproducible
