Hi, a065c70489e96aa254089a666c0a6fcc89c50825 is the latest working hash, the next cab9e353192b34a411122e718c8810e7cc342d29 has this bug on WK1, so I updated the bots to a065c70489e96aa254089a666c0a6fcc89c50825 and it will be the hash of the next week.
Here is a bug report to track what happens near Qt5: https://bugs.webkit.org/show_bug.cgi?id=77653 I updated the build script too: https://github.com/ossy-szeged/qt5-tools In the future we will need a better way for update, because nowadays there are zillion bugs in Qt5 which make the update horror week by week. :-/ I started to write a script (buildbot-light) to build all CI marked Qt5 hash and then build WebKit with it and run layout/API tests on WK1/WK2. But I think it would be better if CI runs WK regression tests too. br, Ossy Osztrogonac Csaba írta:
Please don't update your Qt5 if you didn't do that, because there are a bug in it which made many tests crash on WK1. UInfortunately I didn't notice it before updating. :( I'm searching the latest working hash now.
_______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
