Open Cynical-Optimist opened 4 years ago
In GitLab by [Gitlab user @bochecha] on Aug 29, 2018, 21:46
changed the description
In GitLab by [Gitlab user @tristanvb] on Dec 10, 2018, 10:43
[Gitlab user @bochecha], since this incident, we have implemented a few fixes to the local and remote cache expiry, and also implemented the batch file upload/download optimizations, and we haven't seen this kind of hang in bst pull
tasks in a while.
Can you confirm whether you still see this hang happening or not ? Otherwise will will close this in the near future...
In GitLab by [Gitlab user @bochecha] on Jan 8, 2019, 21:59
[Gitlab user @tristanvb] somehow I wasn't notified for your comment, and I just randomly stumbled upon it. :confused:
I assume you mean it's been fixed in master?
I'm using 1.2.3, and just now it happened again: just now, bst has been pulling desktop/llvm6.bst
(from Freedesktop SDK) for 1h 15min. My ~/.cache/buildstream
hasn't grown at all for the past 25 minutes.
In GitLab by [Gitlab user @valentindavid] on Jan 25, 2019, 15:38
This is happening now repetitively on Freedesktop SDK builders.
In GitLab by [Gitlab user @valentindavid] on Jan 25, 2019, 16:02
The x86 builders are in the US. The cache server is in Netherlands.
In GitLab by [Gitlab user @valentindavid] on Jan 25, 2019, 16:31
The issue with Freedesktop SDK builders was probably not related. We figured out that the bandwidth between the machines was little.
In GitLab by [Gitlab user @abderrahimk] on Jul 2, 2020, 10:55
mentioned in merge request !1979
See original issue on GitLab In GitLab by [Gitlab user @bochecha] on Aug 29, 2018, 21:43
Summary
In the freedesktop SDK, we have a
desktop-platform-image.bst
element:It usually takes me about an hour to pull the artifacts for this element (which I already find incredibly slow, but that might be #554).
This time it's been pulling for almost 4 hours though…
Steps to reproduce
This is the first time it happens to me, so I don't think you might reproduce it easily.
But clone the freedesktop-sdk repo then:
In case it helps, I'm on revision 4f415382919437f9f0b89037d893c4e6ff25031a from that repo (but I don't think it will help reproduce it).
What is the current bug behavior?
Buildstream is pulling, seemingly forever.
My
~/.cache/buildstream/
is not growing at all.What is the expected correct behavior?
This should have finished pulling about 3 hours ago.
Relevant logs and/or screenshots
The
pull.log
is completely unhelpful:Here's a
strace
of the parent/monitoring Buildstream process:That just repeats over and over again.
Now here's what the child process says:
That also seems to be repeating, but much faster.
The child process doesn't seem to be downloading anything at all.
Other relevant information
This is with Buildstream 1.1.7.