Re: sjavac problems continue

I've noted this as well. We should probably store the port file in /tmp, instead of in the build directory. /Magnus > 24 feb. 2016 kl. 19:17 skrev Andreas Lundblad : > >> On Wed, Feb 24, 2016 at 09:33:55AM +0100, Thomas Stüfe wrote: >> Just to add another small

Re: sjavac problems continue

On 25/02/2016 4:14 AM, Andreas Lundblad wrote: On Wed, Feb 24, 2016 at 12:00:36PM +1000, David Holmes wrote: I just had a failed JPRT build on Solaris sparc caused by: Sorry to hear this. I've been ill today (not sure how I'll feel tomorrow) but I'll look into this issue before doing

Re: sjavac problems continue

Hi Andreas, On Wed, Feb 24, 2016 at 7:17 PM, Andreas Lundblad < andreas.lundb...@oracle.com> wrote: > On Wed, Feb 24, 2016 at 09:33:55AM +0100, Thomas Stüfe wrote: > > Just to add another small annoyance, it seems that if I build on Windows > in > > cygwin and I cancel the build for whatever

Re: sjavac problems continue

On Wed, Feb 24, 2016 at 09:33:55AM +0100, Thomas Stüfe wrote: > Just to add another small annoyance, it seems that if I build on Windows in > cygwin and I cancel the build for whatever reason with CTRL+C, the sjavac > server hangs and blocks the output directory. It takes some minutes for it > to

Re: sjavac problems continue

On Wed, Feb 24, 2016 at 12:00:36PM +1000, David Holmes wrote: > I just had a failed JPRT build on Solaris sparc caused by: Sorry to hear this. I've been ill today (not sure how I'll feel tomorrow) but I'll look into this issue before doing anything else. There's always the

Re: sjavac problems continue

Just to add another small annoyance, it seems that if I build on Windows in cygwin and I cancel the build for whatever reason with CTRL+C, the sjavac server hangs and blocks the output directory. It takes some minutes for it to timeout, or I go hunting for the process in Process Explorer. I