-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"phantom" builds #168
Comments
and indeed the first worker I checked had this in it's screen session:
this nicely matches 56h ago now (feb 21)... so somehow the worker should, ahem, behave differently. As in restart all over... |
for the record, this happened yesterday again on two workers... |
Are there any child processes under |
I'll try to remember to look the next time(s) I see this happening. :-) |
I also notice that on armhf, which has 5 workers, there are those 2 haskell builds going on since 56h and 3 other builds. So this might be an issue with rebuilder-worker... investigating now but also filing this issue now... :)
The text was updated successfully, but these errors were encountered: