Closed Bug 1275796 Opened 8 years ago Closed 8 years ago

Logviewer says that every log "no longer exists or has expired"

Categories

(Tree Management :: Treeherder, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: philor, Assigned: wlach)

References

Details

Attachments

(2 files)

e.g. https://treeherder.mozilla.org/logviewer.html#?job_id=28723188&repo=mozilla-inbound#L1628 from about three hours ago, though the same is true of the very most recent failed run, or one from Tuesday, or staging: "The log no longer exists or has expired."
Bug 1273231 performed a schema change. As part of that landing, incoming logs are saved to a new table, and a migration script was run to move over old rows. I suspect that script just hadn't finished running when you checked, since the link in comment 0 now works for me. 

Will, do you know what time the script finished running? :-)

Sorry if this caused disruption - another time we'll try to give you a bit more heads up.
Blocks: 1273231
Flags: needinfo?(wlachance)
Priority: -- → P1
Oh, maybe a dupe of bug 1271763?
Possibly.

Similar to that bug, the STR were incomplete (hence the WFM above). See bug 1271763 comment 2.

The key part is to click a log step top right, to try and load the log. The page (and the error summary) loads fine.
No I mean:

STR in both bugs implied the problem was that the log viewer couldn't find the job/error summary etc. Which is why I said WFM.

More complete STR (linked above) show what the actual problem is, and yes I see that problem too.
(In reply to Ed Morley [:emorley] from comment #1)
> Bug 1273231 performed a schema change. As part of that landing, incoming
> logs are saved to a new table, and a migration script was run to move over
> old rows. I suspect that script just hadn't finished running when you
> checked, since the link in comment 0 now works for me. 
> 
> Will, do you know what time the script finished running? :-)
> 
> Sorry if this caused disruption - another time we'll try to give you a bit
> more heads up.

The migration actually completed before I switched things over with minimal disruption, but it looks like this is another problem with the logslice API that I missed.
Flags: needinfo?(wlachance)
Assignee: nobody → wlachance
Comment on attachment 8756846 [details] [review]
[treeherder] wlach:1275796 > mozilla:master

Sorry for the trouble, I should have tested this more thoroughly.
Attachment #8756846 - Flags: review?(emorley)
Comment on attachment 8756846 [details] [review]
[treeherder] wlach:1275796 > mozilla:master

Have filed bug 1275903 for adding tests for the log slice API, since we've never had any.
Attachment #8756846 - Flags: review?(emorley) → review+
Keywords: autoland
Pull request has landed in master: https://github.com/mozilla/treeherder/commit/dc3c65545a61100c4efd79be5a31309000eef174
Status: NEW → RESOLVED
Closed: 8 years ago
Keywords: autoland
Resolution: --- → FIXED
Ah, the failure in my STR was a failure to realize that we stick the unworkable second hash onto a URL that we've loaded without it. Click a failed job, click the icon for the log, you load https://treeherder.mozilla.org/logviewer.html#?job_id=28771245&repo=mozilla-inbound which shows the "no longer exists or has expired" but by the time you copy it, the URL has been changed to https://treeherder.mozilla.org/logviewer.html#?job_id=28771245&repo=mozilla-inbound#L3942 which when loaded does not.
Ah yes I had the same confusion in bug 1271763 comment 1.

I've filed bug 1275909 for fixing the log viewer line anchors to avoid that problem.
Commit pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/34b9c631cfa9edef01492dcfc7be2bddbe13ee15
Bug 1275796 - Travis: Revert change to apt-get command

One instance was fixed after review comments, this changes the other.
Bah that was meant to be bug 1275425.
Commits pushed to master at https://github.com/mozilla/treeherder

https://github.com/mozilla/treeherder/commit/5870b1d49556b410c25b8c38da8ef713ed9408aa
Bug 1275796 - Fix logslice API with taskcluster logs

Taskcluster logs use the name 'builds-4h'

https://github.com/mozilla/treeherder/commit/2d711b5dbbb75e7aa7d16ee6f3e50772bf28e833
Merge pull request #1520 from wlach/1275796-2

Bug 1275796 - Fix logslice API with taskcluster logs
Component: Treeherder: Log Viewer → TreeHerder
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: