Re: [webkit-dev] WebKit Transition to Git

On Mon, Oct 5, 2020 at 6:22 AM Frédéric Wang wrote: > One thing to take into account is that WebKit's repository is big and > public GitHub/GitLab prevent creating large repository by default. This > means it might not be possible for contributors to actually fork > WebKit's repository on their

Re: [webkit-dev] Supporting for finding ref tests

MANIFEST.json mostly stays out of the way / happens under the hood. It is cached as GitHub releases, and ignored by .gitignore. One of its purposes is a cache of the reftest graph. Once you run any test or explicitly run `./wpt manifest`, the manifest will be generated/updated in the root of your

Re: [webkit-dev] Supporting for finding ref tests

WPT has recently passed an RFC trying to simplify the reftest graph (although it has not been implemented yet), which eliminates a lot of the complexities and concerns. On Fri, Nov 8, 2019 at 5:07 PM Ryosuke

Re: [webkit-dev] Moving to Python 3

Any thoughts on bytes and Unicode strings, especially the string literals in the code base? On Fri, Jul 12, 2019 at 3:38 PM Tim Horton wrote: > > > On Jul 12, 2019, at 12:18 PM, Jonathan Bedard wrote: > > Hello WebKit developers, > > Now that the Catalina developer seeds are available, it is

Re: [webkit-dev] Standard process for exporting new WPT tests?

Current maintainer of Chromium's WPT sync chiming in: Because of the lack of atomic operations across two separate repos, some kind of transient inconsistency and race conditions are unavoidable. FWIW, when Chromium's WPT sync was originally designed, there was concern about increasing the wait

Re: [webkit-dev] Upstreaming from LayoutTests to web-platform-tests, coordinating Blink+WebKit

On Fri, Nov 24, 2017 at 9:09 AM, Frédéric WANG wrote: > Right, running all the tests is nice. But sometimes I personally feel > guilty to have to execute everything on EWS for example to retrieve > results for macOS/iOS (when I did not have access to a mac) or to fix >