| Summary: | run-webkit-tests spends 20-30 seconds "building" ImageDiff | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Jonathan Bedard <jbedard> | ||||
| Component: | Tools / Tests | Assignee: | Jonathan Bedard <jbedard> | ||||
| Status: | RESOLVED DUPLICATE | ||||||
| Severity: | Normal | CC: | ap, darin, ews-watchlist, glenn, thorton, webkit-bug-importer | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
Jonathan Bedard
2020-09-02 14:52:04 PDT
Created attachment 407819 [details]
Patch
Comment on attachment 407819 [details]
Patch
Won't _path_to_image_diff (which is @memoize'd) store the failure to find it in check_image_diff, and return that after we build it (thus making ImageDiff not found if it got built)?
(In reply to Tim Horton from comment #3) > Comment on attachment 407819 [details] > Patch > > Won't _path_to_image_diff (which is @memoize'd) store the failure to find it > in check_image_diff, and return that after we build it (thus making > ImageDiff not found if it got built)? Likely yes, the right solution is probably to clear out the memoization, but our current @memoize doesn't support that Isn't bug 204420 the root cause here? (In reply to Alexey Proskuryakov from comment #5) > Isn't bug 204420 the root cause here? Do you mean "isn't this a dupe of that"? I think the answer is "yes"! *** This bug has been marked as a duplicate of bug 204420 *** |