Failure at rung of get_source on windows with cygwin
Simonovsky, Pavel
Pavel_Simonovsky at bmc.com
Sun Jan 27 08:36:48 UTC 2019
10x a lot. Will try it.
I was looking for something like that - kind of tar ball with whole source...
-----Original Message-----
From: Aleksey Shipilev [mailto:shade at redhat.com]
Sent: Saturday, January 26, 2019 12:03 PM
To: Magnus Ihse Bursie <magnus.ihse.bursie at oracle.com>; Simonovsky, Pavel <Pavel_Simonovsky at bmc.com>; build-dev at openjdk.java.net
Subject: Re: Failure at rung of get_source on windows with cygwin
On 1/25/19 10:39 PM, Magnus Ihse Bursie wrote:
> On 2019-01-25 22:12, Simonovsky, Pavel wrote:
>> I am failing at windows build on step of running get_source.sh:
>>
>> nashorn: abort: stream ended unexpectedly (got 1297
>> bytes, expected 192443)
>> jaxws: abort: stream ended unexpectedly (got 1957
>> bytes, expected 21072)
>> jaxp: rollback completed
>> hotspot: abort: stream ended unexpectedly (got 99623
>> bytes, expected 483101)
>> jaxp: abort: stream ended unexpectedly (got 28110
>> bytes, expected 37505)
>> langtools: transaction abort!
>> langtools: rollback completed
>> langtools: abort: stream ended unexpectedly (got 810
>> bytes, expected 2288)
>> WARNING: /tmp/forest.34500/hotspot.pid.rc exited abnormally.
>> WARNING: /tmp/forest.34500/jaxp.pid.rc exited abnormally.
>> WARNING: /tmp/forest.34500/jaxws.pid.rc exited abnormally.
>> WARNING: /tmp/forest.34500/langtools.pid.rc exited abnormally.
>> WARNING: /tmp/forest.34500/nashorn.pid.rc exited abnormally.
>>
>> I have enough disk space:
>>
>> $ df -k .
>> Filesystem 1K-blocks Used Available Use% Mounted on
>> C: 248548552 191203664 57344888 77% /cygdrive/c
>>
>> And fast network connection.
>> What have I to do to troubleshoot this problem?
> It sounds like the unfortunately well-known problems of
> underperforming mercurial server at hg.openjdk.java.net, combined with
> some issues with mercurial running on cygwin. :-(
>
> The only advice I can give is to keep re-trying. Eventually you will
> get a clone, and subsequent operations will go smoother. If you have a
> forest on a local linux machine, try starting by making a clone
> manually from that one. (You'll need to clone each repo individually.)
Or take this, Pavel:
https://builds.shipilev.net/workspaces/
-Aleksey
More information about the build-dev
mailing list