Store whether a test is slow on TestInput

• Component: Tools / Tests
• Status: RESOLVED FIXED

[Sam Sneddon [:gsnedders]]

Bug 161626 introduced test-objects.json, however no test-objects.json files were ever added and this has thus been permanently dead code. Given it's lack of usage, let's remove it.

Additionally, with it gone, the expectations is once against the canonical source of knowledge about whether a test is slow and we don't need to communicate this through all the various components.

[Sam Sneddon [:gsnedders]]

Created attachment 426022 [details]
Patch

[Sam Sneddon [:gsnedders]]

Somehow I totally missed the file (did I look in Tools or something equally silly?), and this is in fact used. Hmm. I wonder what to do here instead; having two different places where we store this metadata (especially within webkitpy's data model) is somewhat clumsy and annoying.

[Jonathan Bedard]

(In reply to Sam Sneddon [:gsnedders] from comment #2)
> Somehow I totally missed the file (did I look in Tools or something equally
> silly?), and this is in fact used. Hmm. I wonder what to do here instead;
> having two different places where we store this metadata (especially within
> webkitpy's data model) is somewhat clumsy and annoying.

Seems like all the effected tests are http tests....is there any reason we can't convert them to normal test expectations?

[Radar WebKit Bug Importer]

<rdar://problem/76969468>

[Sam Sneddon [:gsnedders]]

Created attachment 429110 [details]
Patch

[Sam Sneddon [:gsnedders]]

(In reply to Jonathan Bedard from comment #3)
> (In reply to Sam Sneddon [:gsnedders] from comment #2)
> > Somehow I totally missed the file (did I look in Tools or something equally
> > silly?), and this is in fact used. Hmm. I wonder what to do here instead;
> > having two different places where we store this metadata (especially within
> > webkitpy's data model) is somewhat clumsy and annoying.
> 
> Seems like all the effected tests are http tests....is there any reason we
> can't convert them to normal test expectations?

We could, though there was concern about bloating TestExpectations with WPT before.

I think some of this is also related to the fact they'd need to be marked as slow in _every_ TestExpectations file, unless I'm misremembering how platform-specific expectations are added.

That said, this new patch does a bunch of refactoring that we need to do anyway, and with that done it becomes pretty easy to support tests-options.json again.

[EWS]

Committed r277781 (237942@main): <https://commits.webkit.org/237942@main>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 429110 [details].