You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Curious fact: the last package worker1 was processing was python310Packages.mmengine. The previous time python310Packages.mmengine was processed was October 14, and examining https://r.ryantm.com/log/~workers/ shows that worker2 went AWOL for a briefer time on October 14 (the last modified time for its log file is substantially before midnight), immediately after processing the same package. Out of a queue of 20,000+ packages (currently), that's a pretty suspicious coincidence, but I don't know what to make of it yet.
I'd be curious to know what the status of the worker1 service on build02 is right now, and if there are any journal messages that shed light on why it's stuck.
The text was updated successfully, but these errors were encountered:
There are no log files for worker1 in https://r.ryantm.com/log/~workers/ since Monday.
Curious fact: the last package worker1 was processing was
python310Packages.mmengine
. The previous timepython310Packages.mmengine
was processed was October 14, and examining https://r.ryantm.com/log/~workers/ shows that worker2 went AWOL for a briefer time on October 14 (the last modified time for its log file is substantially before midnight), immediately after processing the same package. Out of a queue of 20,000+ packages (currently), that's a pretty suspicious coincidence, but I don't know what to make of it yet.I'd be curious to know what the status of the worker1 service on build02 is right now, and if there are any journal messages that shed light on why it's stuck.
The text was updated successfully, but these errors were encountered: