Good moaning, It looks like core OBS has serious stability issues with its API service. This seems to have been masked by the http downtimes so far. There are still frequent, albeit mostly shorter, downtimes of the whole OBS as seen over http(s), but the major problem as seen from linked OBS perspective is that the API remains inaccessible after such downtimes.
Core OBS has been in such a state now since: "Sat Aug 20 04:02:56 UTC 2011". The overall downtime for the last 7 days probably exceeds 3 days. I have now filed bug 22702 ( https://bugs.meego.com/show_bug.cgi?id=22702 ). Cheers Thomas PS: It took me a bit to find the right mailing list for this. ReleaseEngineering officially names meego-releases as primary contact, but according to the info blurb: “Anyone can subscribe to the list, but posting is moderated and limited only to people who publish MeeGo release information. For open discussion about anything posted here, you can take those discussions to meego-dev or meego-packaging as appropriate.” In the end I went with meego-packaging as that is explicitly named on http://build.meego.com/ “Please join our mailing list [...] for discussions around the Build Service.” I’ve CC’d meego-dev and meego-community as the impact for community OBS is high and issues have been discussed on both previously, post FOLLOW-UPS to meego-packaging though, please! I've also CC'd Adam as he is the only person who visibly said they would work on the previous OBS issue. _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
