Hi,
It doesn't seems to be so important for Nokia, because on
QtWebKit 2.2 branch there are many failing API tests too:
- QtWebKit2.2-branch x86-32 Linux Release Qt 4.7.x: 5 failing tests
- QtWebKit2.2-branch x86-32 Linux Release Qt 4.8.x: 7 failing tests
- QtWebKit2.2-branch SnowLeopard Intel Release: 12 failing tests
They aren't new regressions, they are at least a month old bugs.
And we don't mentioned the trunk, 64 bit platform, Symbian, ...
br,
Ossy
Benjamin Poulain írta:
They are important.
The problem is we are currently understaffed due to an internal Nokia
project taking lots of engineers.
I suggest to add "expected failure" exceptions for the failing tests.
And create a P1 tasks for each one.
Failing API tests are particularly dangerous for releases. It is one of
the focus of QtWebKit 2.2. Anyone is welcome to help on this problem.
cheers,
Benjamin
_______________________________________________
webkit-qt mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
