September 2019 - webkit-dev - lists.webkit.org

Emojis for builder vs tester in EWS status-bubbles
by Aakash Jain 13 Sep '19

13 Sep '19

Hi Everyone, We had this long-standing issue with the EWS bubbles that many engineers were confused whether a queue was build-only, test-only or build-and-test. For e.g.: https://webkit.org/b/152790 Simon Fraser 2016-01-06: "From the EWS bubbles you can't tell if a bot is a build-only bot, or a build-and-test bot. All this time I've been assuming that GTK was running tests, and that assumption was wrong." To solve that, we recently added emojis in the status-bubbles. Builder queues will only have builder emoji, tester queues will only have tester emoji, and build-and-test queues will have both builder and tester emojis. Also, we have separated most of the build-and-test queues into separate builder queues and tester queues. These changes should help in clarifying which queue does what. The emojis we have used are: Builder: 🛠️ (https://emojipedia.org/hammer-and-wrench/) Tester: 🔬 (https://emojipedia.org/microscope/) The emoji for tester doesn't feel very appropriate, and I am curious to know if anyone has a better suggestion. I previously used 🧪 (https://emojipedia.org/test-tube/) but this emoji was added to Unicode last year only, and older OSes don't have this emoji. So I switched to the current (microscope) emoji in https://webkit.org/b/201532. Please let me know if anyone has suggestions for better emojis. If not, atleast this email would let people know the purpose of these emojis. Thanks Aakash

2 1

EWS Watchlist
by Aakash Jain 11 Sep '19

11 Sep '19

Hi Everyone, For those who don't know we have a cool little feature named watchlist, which allows you to monitor any particular code in WebKit repository. You can specify the files/folders to monitor (in https://trac.webkit.org/browser/webkit/trunk/Tools/Scripts/webkitpy/common/… <https://trac.webkit.org/browser/webkit/trunk/Tools/Scripts/webkitpy/common/…>), and whenever any patch modifies those, EWS would cc you on that bug. Watchlist was partially broken for a while (because of containing incorrect email addresses). I just fixed it in https://bugs.webkit.org/show_bug.cgi?id=201433 <https://bugs.webkit.org/show_bug.cgi?id=201433>. So, now you might see EWS cc'ing bunch of people, more frequently than previously. Thanks Aakash

1 0

CI builds fail on all platforms with "ReferenceError: Can't find variable: WebAssembly"
by Eike Rathke 06 Sep '19

06 Sep '19

Hi, our CI builds keep failing on all platforms with the following messages: Running stress/web-assembly-constructors-should-not-override-global-object-property.js.default Running stress/web-assembly-constructors-should-not-override-global-object-property.js.mini-mode stress/web-assembly-constructors-should-not-override-global-object-property.js.mini-mode: Exception: ReferenceError: Can't find variable: WebAssembly stress/web-assembly-constructors-should-not-override-global-object-property.js.mini-mode: global code@web-assembly-constructors-should-not-override-global-object-property.js:2:12 stress/web-assembly-constructors-should-not-override-global-object-property.js.default: Exception: ReferenceError: Can't find variable: WebAssembly stress/web-assembly-constructors-should-not-override-global-object-property.js.default: global code@web-assembly-constructors-should-not-override-global-object-property.js:2:12 stress/web-assembly-constructors-should-not-override-global-object-property.js.default: ERROR: Unexpected exit code: 3 FAIL: stress/web-assembly-constructors-should-not-override-global-object-property.js.default stress/web-assembly-constructors-should-not-override-global-object-property.js.mini-mode: ERROR: Unexpected exit code: 3 FAIL: stress/web-assembly-constructors-should-not-override-global-object-property.js.mini-mode The exceptions look quite similar to the output given at https://bugs.webkit.org/show_bug.cgi?id=192020 Eike -- GPG key 0x6A6CD5B765632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A

3 2

Introducing brand new EWS
by Aakash Jain 04 Sep '19

04 Sep '19

Introducing brand new EWS with EWS for API Tests (for macOS and iOS) and EWS for WebKitPerl Tests! Starting today, when you upload a patch to bugs.webkit.org <http://bugs.webkit.org/>, you will see few more bubbles (for API tests and webkitperl tests). You might also see additional button 'Submit to new EWS' (if the patch doesn't have r? flag). The new EWS comes with many new features and there are lot more I want to add. But, I don't want you guys to wait more to start getting the benefits. That's why I am rolling it out in phases, starting with EWS for API Tests and WebKitPerl Tests. These are tests which are not currently covered by the existing EWS. Next step would be to move queues from existing EWS to new EWS one by one, with the eventual goal of moving over everything to new EWS. Why new EWS? The existing EWS has certain architectural limitations. One of the prominent limitation is that there is no concept of building and testing the patch on different queues. If we have three queues: WK1 tests, WK2 tests and API tests, all three queues would need to compile WebKit independently. So WebKit would be compiled thrice instead of once. This is inefficient and thereby require more hardware. The new EWS has separate builder and tester queues. Builder queues build once and upload the archive. Multiple tester queues download that same archive and run tests on that. That way WebKit is compiled only once, and re-used on multiple tester queues. This improves system efficiency and allows us to add new test queues with substantially less hardware. The new EWS uses Buildbot at the back-end, which is a production-level CI system. It is easier to maintain and automatically provide various features like historical build logs, real-time log streaming, easier bot management, ability to retry a build etc. Plus, it’s a system most of you are already familiar with (build.webkit.org <http://build.webkit.org/>). How can you contribute: If you are interested in contributing, the source code is located at: ews-build (Buildbot): Tools/BuildSlaveSupport/ews-build ews-app (web-app): Tools/BuildSlaveSupport/ews-app Detailed instructions are at: https://trac.webkit.org/wiki/EarlyWarningSystem#ContributingtoEarlyWarningS… <https://trac.webkit.org/wiki/EarlyWarningSystem#ContributingtoEarlyWarningS…> Upcoming features: - status-bubble should display position in queue https://bugs.webkit.org/show_bug.cgi?id=196607 <https://bugs.webkit.org/show_bug.cgi?id=196607> - EWS should comment on Bugzilla bugs about failures https://bugs.webkit.org/show_bug.cgi?id=196598 <https://bugs.webkit.org/show_bug.cgi?id=196598> - EWS should have a way to retry a patch https://bugs.webkit.org/show_bug.cgi?id=196599 <https://bugs.webkit.org/show_bug.cgi?id=196599> - Security EWS https://bugs.webkit.org/show_bug.cgi?id=196605 <https://bugs.webkit.org/show_bug.cgi?id=196605> If you notice any issue, please feel free to file bugs (and assign to me). Thanks & Regards Aakash Jain

3 8

Logging in iOS simulator
by Ken Russell 03 Sep '19

03 Sep '19

Hi WebKit developers, Is it possible to log from the WebKit build for the iOS Simulator? I've had difficulty getting LOG() statements to work even on macOS, so just tried NSLog, but the result didn't show up in the system log when opened from the simulator. Thanks, -Ken

2 2

Catalina and Xcode setup problems
by Rob Buis 02 Sep '19

02 Sep '19

Hi, I recently tried Catalina beta 7 and Xcode 11.0 beta 7 and ran into some problems. When running mini-browser loading fails in WK2 (works for WK1) with the following Inspector message: Failed to load resource: A server with the specified hostname could not be found. Also many loading related tests fail or timeout. Did anybody try a similar setup or can tell if I missed a setup step? Could it be a sandbox issue and/or is Python 2 or 3 choice important? Cheers, Rob.

1 0