WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED DUPLICATE of
bug 223216
227928
Can't access WinCairo test results
https://bugs.webkit.org/show_bug.cgi?id=227928
Summary
Can't access WinCairo test results
Alex Christensen
Reported
2021-07-13 16:25:06 PDT
When I go to
https://build.webkit.org/results/WinCairo-64-bit-WKL-Debug-Tests/r279815%20(689)/results.html
then click on the diffs, I get 403 errors. The solution apparently has to do with changing the umask or chmod or something.
Attachments
Add attachment
proposed patch, testcase, etc.
Aakash Jain
Comment 1
2021-07-13 16:28:37 PDT
The individual files created by the wincairo bots have very restrictive file permissions. We simply unzip the results and host them. The bots (probably buildbot.tac for buildbot-worker) should use umask = 022
Don Olmstead
Comment 2
2021-07-13 16:31:06 PDT
We are using that umask any other things to look at?
https://github.com/WebKitForWindows/docker-webkit-dev/blob/master/buildbot/WebKit-BuildWorker/buildbot.tac.tmpl#L35
Fujii Hironori
Comment 3
2021-07-13 18:26:30 PDT
Same issue with this.
Bug 223216
– Forbidden to access WinCairo Buildbot sub-directories of layout test results as "403 Forbidden"
Alexey Proskuryakov
Comment 4
2021-07-13 22:51:52 PDT
Perhaps it should be 0o022, as changed for Python 3 in
https://trac.webkit.org/changeset/268935/webkit
?
lingho@apple.com
Comment 5
2021-07-16 16:54:21 PDT
I went ahead and applied the ACL to WinCairo-64-bit-WKL-Debug-Tests/ directory, similar to what's done in
https://bugs.webkit.org/show_bug.cgi?id=223216
Don Olmstead
Comment 6
2021-07-16 17:46:54 PDT
The test results Alex linked to aren’t 403ing anymore so this looks successful. Should check after more builds before closing it. Thanks for the assist!
Fujii Hironori
Comment 7
2021-07-20 12:58:53 PDT
*** This bug has been marked as a duplicate of
bug 223216
***
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug