XFCE bugwatches appear to be broken

Bug #816340 reported by Graham Binns
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

I was going through my bug list to see if some would need retesting against the second alpha release of 11.10. One of those is bug #348904, which is also tracked upstream on the remote bug-tracker "bugzilla.xfce.org".

Upstream has marked this bug as "RESOLVED FIXED", but in launchpad has it still in "Confirmed" status. When I tried to correct the status, launchpad reported it could not connect to the remote bug-tracker. ("Launchpad couldn't connect to Xfce Bugzilla.") According to the error-help page (https://bugs.launchpad.net/bugs/348904/+watch/53980/+error-help#CONNECTION_ERROR) I first needed to check if the bug-tracker is on-line, which is the case. Secondly it tells me to report it here to let you know.

Revision history for this message
Graham Binns (gmb) wrote :

I've just looked at the XFCE bug watches (https://bugs.launchpad.net/bugs/bugtrackers/xfce-bugs). It seems that many of them have not updated at all, but no errors are showing in their activity logs. We need to take a look at the checkwatches log files to find out what's going on.

Revision history for this message
Graham Binns (gmb) wrote :

Today's checkwatches logs include:

2011-07-25 13:08:21 INFO Updating 114 watches for 100 bugs on http://bugzilla.xfce.org
2011-07-25 13:08:24 INFO Error updating http://bugzilla.xfce.org/: http://bugzilla.xfce.org: HTTP Error 500: Internal Server Error

I'll investigate further with a local instance to see if I can reproduce the problem.

Revision history for this message
Graham Binns (gmb) wrote :

I can reproduce the problem locally by creating a bugwatch against the XFCE bugzilla and running checkwatches manually. I haven't been able to isolate the cause of the 500 error yet (sidebar: we need to handle HTTP 500 errors better; they should probably go in the activity log for the watch).

Marking this as Triaged since there's definitely a problem.

Changed in launchpad:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Gary M (garym) wrote :

Not sure if this is the same issue - xfce bugzilla bugs are being assumed by launchpad to be http, which fails from a browser whereas https works fine.

Revision history for this message
Linard Verstraete (linardv) wrote :

The details of the xfce bug tracker in launchpad were updated to connect to https. But still, after 48 hours non of the xfce bugs were updated successfully...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.