681874 - Hack around tbplbot commenting with tbpl.mozilla.org/php/getParsedLog.php log links

Status: RESOLVED WORKSFORME

(Tree Management Graveyard :: TBPL, defect)

Description

[Phil Ringnalda (:philor)]

I know we discussed this somewhere, because I remember agreeing that for just a few days, it was better to have tbplbot comment with broken links than to comment with links that would soon be outdated.

I no longer think that's reasonable. We now have 108 bugs with comments including "tbpl.mozilla.org/php/getParsedLog", and if you don't know that you have to invert the mozilla, those appear to just be useless 404 links. Since it's probably going to be more like months than days or weeks, we should switch tbpl.allizom to commenting with tbpl.allizom links.

Comment 1

[Arpad Borsos [:Swatinem]]

Another thing we need to clarify is how long to keep these logs. Do they expire after a few month? With that in mind, they will all become 404s anyway.

Comment 2

[Phil Ringnalda (:philor)]

Yep, I did wonder about that, but that's a totally separate thing. I'm talking about the kind of thing that just happened for the fourth or fifth time, where I starred a failure and the person interested in that test asked me on IRC why I was starring with a link that just gives a 404, so they couldn't see the failure. I'm also interested in 30 days, when Tinderbox logs currently go away, and 60 and 90 and 180 days, when I quite often want to see a log for info that didn't make it into the bug, but here I'm talking about 5 or 10 minutes, however long it takes for a developer who thinks they have fixed a failure to read their bugmail and say "wtf, was that really this bug or did philor misstar?"

Comment 4

[Phil Ringnalda (:philor)]

No longer a problem, now that we're deployed on tbpl.m.o