Summary: | Leaks bot should use WebKit2 | ||
---|---|---|---|
Product: | WebKit | Reporter: | Andreas Kling <kling> |
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | ap, kling, lforschler |
Priority: | P2 | ||
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Description
Andreas Kling
2017-02-04 23:53:08 PST
Actually, I'm really lost in how the bots are set up, so I'm unassigning it from myself. @Alexey: do you agree that we should do this, and if so, do you think it would be easy? I agree that testing wk2 would be much better. Reconfiguring bots is easy, but first, we need to figure out how to do this in principle. A naive approach would result in only seeing UI process leaks. Unrelated to this, we should switch the bot to Sierra ASAP. It has a fix for a huge networking leak that adds a lot of noise. I'll take care of this. Absolutely agreed about Sierra. A slightly less naive approach could simply run "leaks" on each of our processes (WKTR, WebContent, Networking, Databases) and concatenate the results. I think it would still be useful, and we'd want to see leaks in all processes anyway. |