On Sep 2, 2015, at 3:42 PM, David Evans wrote: > It wasn't taking the password for me either so I did something else for 20 > minutes or so and then it succeeded. I sent > the message to you rather than admin as I understand that you are > coordinating with them. The way things are going, no > need to confuse things any more than necessary. :-) Seems like our network > services at Apple are pretty fragile right > now although looks like some small improvement with the buildbots today.
I am only coordinating with the Mac OS Forge to the extent that I report problems to that email address, and then after a few days I send another message asking for a response to the first message, and so on. My guess is things are no more fragile at Mac OS Forge than they've ever been, but in the past we've had an admin who was actively looking after things such as making sure disks don't fill up, letting us know about planned downtimes, and also responding in a timely manner when we report outages and other issues. I don't see any improvement with the buildbot today. The buildbot master was brought back online a week ago, but the Snow Leopard and Lion buildbot slaves continue to have corrupted MacPorts registries (possibly due to their disks filling up) and the Mountain Lion slave has a Subversion exception. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
