There are several tests in media/track that have been block-skipped. This patch will individually skip them so that we can start to add new tests to the media/track folder without skipping them. The existing tests don't run successfully because not enough functionality has been implemented. My general strategy going forward will be to include new, simpler tests that exercise only the functionality of each new patch as it is added. I will enable the tests that are skipped now as their required functionality becomes available in the future.
Created attachment 112713 [details] Patch
Instead of skipping them, why don't we just check them in with failing results. That way, when you make them pass, we can see the progression?
Not a bad idea. My only concern is that there are so many of them that future (incremental) patches will then contain lots of test updates. Is that preferable from a reviewers perspective? Either way is fine with me.
Comment on attachment 112713 [details] Patch @Sam: I believe because they time out rather than running to completion.
Incremental test updates are fine (good even) because they help us understand how patches change behavior. You list tests as timing out though, which causes a problem if they're slowing down the test suite.
Potential solution: skip them for now because they time out. After I implement events, the tests won't time out anymore, but their results won't be perfect either. At that time, I'll unskip them and commit some failing results that can change with further progressions. Sound good?
Sounds good to me.
Comment on attachment 112713 [details] Patch Clearing flags on attachment: 112713 Committed r98642: <http://trac.webkit.org/changeset/98642>
All reviewed patches have been landed. Closing bug.