Closed Bug 576981 Opened 15 years ago Closed 13 years ago

Don't cache Tinderbox log fetches with non-success codes

Categories

(Tree Management Graveyard :: TBPL, defect)

Product:
Tree Management Graveyard
Component:
TBPL
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

Details

During Tinderbox's rather frequent bouts of overload, when requesting a log will spin and spin and then eventually give a 500 Internal Server Error, if anyone tries to get tbpl to load a summary and tbpl gets the 500, it will cache it and then continue to serve up a little bitty blue box as the summary to anyone who comes along later.
If we wind up caching the failure to download a log from ftp.m.o, I'll worry about this again then.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.