1335038 - Autophone logs do not display in Treeherder log viewer due to missing CORS header

Status: RESOLVED FIXED

(Testing Graveyard :: Autophone, defect)

Description

[Bob Clary [:bc] (inactive)]

https://treeherder.allizom.org/logviewer.html#?job_id=67391245&repo=try&lineNumber=1453

An error occurred while trying to load the specified log. It may not exist, or may not have any content.

I did get this to work at one time, but it is failing now.

Will, Ed: Is there anything in the logs that will give me a hint as to what I am doing wrong?

Comment 1

[Ed Morley [:emorley]]

The web console is showing:

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://autophone-dev.s3.amazonaws.com/v1/task/RBu7RR9QRRS_dIaO2NMwOw/runs/0/artifacts/public/build/crashtest-crashtests-settings.ini-1-samsung-gs3-3-2ce8b170-889e-47f5-b9a4-3d1e2ef917fe.log. (Reason: CORS header 'Access-Control-Allow-Origin' missing).

Treeherder's log viewer now uses (via an iframe) the Unified log viewer:
https://github.com/taskcluster/unified-logviewer

...which uses service workers to incrementally fetch the log on the client, rather than proxying log content via the Treeherder /logslice/ endpoint.

That bucket will need to set appropriate CORS headers (wildcard should be safe, right?):
https://docs.aws.amazon.com/AmazonS3/latest/dev/cors.html

Comment 2

[Bob Clary [:bc] (inactive)]

Ed, Thanks! I didn't even think of checking my console.

glob: Is this something you can configure or can I do it?

The buckets I use for Autophone are: autophone-dev and autophone

Comment 3

[:glob ✱]

i'll look at this.

Comment 4

[:glob ✱]

CORS headers added to autoland and autoland-dev buckets.

Comment 5

[:glob ✱]

(In reply to Byron Jones ‹:glob› from comment #4)
> CORS headers added to autoland and autoland-dev buckets.

of course i mean autophone and autophone-dev.  there's a prize of $0 if you guess what other similarly named project i've been working on recently.