RESOLVED CONFIGURATION CHANGED 178019
Layout test http/tests/cache/disk-cache/disk-cache-validation-no-body.html is timing out.
https://bugs.webkit.org/show_bug.cgi?id=178019
Summary Layout test http/tests/cache/disk-cache/disk-cache-validation-no-body.html is...
Attachments
Alexey Proskuryakov
Comment 1 2017-10-09 12:58:27 PDT
Is this a regression? I thought that all the tests were supposed to pass in release builds now.
Matt Lewis
Comment 2 2017-10-09 13:25:28 PDT
It looks like after the test was skipped in https://trac.webkit.org/changeset/222994/webkit These tests started to time out as well: http/tests/cache/disk-cache/disk-cache-vary-no-body.html http/tests/cache/disk-cache/disk-cache-vary.html I am testing locally to see if the timeout is still occurring and trying to bisect a possible regression point.
Antti Koivisto
Comment 3 2017-10-09 13:41:15 PDT
Looking at that dashboard numbers, the running time of the test on El Capitan bot has been steadily increasing over the last few weeks until it crossed the 30s threshold.
Antti Koivisto
Comment 4 2017-10-09 13:42:00 PDT
Maybe the bot is choking on something?
Matt Lewis
Comment 5 2017-10-09 13:46:48 PDT
The two test I mentioned before also seem to have go through that process of steadily growing in time.
Alexey Proskuryakov
Comment 6 2017-10-09 13:51:46 PDT
Good catch. There is a known kernel bug (fixed in High Sierra) making processes on WebKit test bots launch slower over time, which has particularly noticeable effect on http tests. These bots have uptime of 21 days, which used to be OK. Perhaps something changed that makes the problem manifest faster now. I suggest unskipping the test, rebooting the bots, and watching this test closely for the next few weeks.
Matt Lewis
Comment 7 2017-10-09 14:49:51 PDT
Ryan Haddad
Comment 8 2017-10-09 17:37:10 PDT
After the unskipping and rebooting, it looks like things are good again on the El Capitan Release bots. Moving this to resolved / config changed.
Radar WebKit Bug Importer
Comment 9 2017-10-09 17:37:36 PDT
Note You need to log in before you can comment on or make changes to this bug.