Re: [service-workers-tests] Cache Storage API tests: Fix WPT test bugs, remove redundant local copies (#5413)

> @sideshowbarker, are you able to tell what happened?

After looking through the logs I’m still not sure what all happened. For one thing, the logs are extremely verbose. Anyway as far as w3c-test.org goes, I do know that *one* problem that happened over the last few days is that we ran out of filesystem space for the `submissions` stuff. 

The mount for the `submissions` directory has 29GB of space but we periodically fill it up to 100% and I have to go in there an manually rm directories for some older PRs until I get it back down to 50% or so. So we need to deal with that chronic problem and yesterday @gsnedders opened https://github.com/w3c/github_sync/pull/20 as part of the solution.

Another chronic problem we have is that webhook requests to w3c-test.org sometimes just timeout (and then don’t get re-tried). I haven’t been able to see a pattern to what causes them to timeout but I guess one way we can deal with it is to try to configure longer timeouts. I think the merger of the CSS tests may be making the timeout problem worse in the cause of the sync/submissions webhook at least.

Anyway in general if you look at the itemization of possible causes in https://github.com/w3c/web-platform-tests/pull/5413#issuecomment-292521246 from @bobholt, there are some of those causes that are easier to identify and troubleshoot and there are some which are a lot harder and more time-consuming to try to do that for.

In those cases I’m not sure what we can do expect re-trigger the webhooks and travis—and just watch/tail the logs when we do.

View on GitHub: https://github.com/w3c/web-platform-tests/pull/5413#issuecomment-293146283

Received on Tuesday, 11 April 2017 04:26:24 UTC