[Webkit-unassigned] [Bug 206579] [CSS Backgrounds] ASSERTION FAILED: !image->size().isEmpty() on css/css-backgrounds/background-size/vector/zero*ratio-auto-5px.html

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=206579

--- Comment #2 from Carlos Alberto Lopez Perez <clopez at igalia.com> ---
(In reply to Alexey Proskuryakov from comment #1)
> It's not really OK to leave 100% crashing tests enabled. 
> 

Sorry, but that I should mark crashing tests as Skip its totally news to me.
And after thinking about that, I don't think its a good practice.

I always mark crashing tests as Crash, for the very same reasons I mark tests failing as Failure, and tests timing-out as Timeout, and not simply skip them:

1) If there its a change in WebKit that makes the test start passing I want to be notified of that (new pass).
2) If the test starts failing (or timing out) instead of crashing I also want to get notified.
3) But if the test its skipped we won't get ever notified of the new behavior until someone manually un-skips it.


> Generating crash
> reports is somewhat costly, and can impact stability of other tests, or
> prevent us from getting crash reports from other tests.

Well, its also costly to mark tests timing-out as Timeout, and not simply skip them.. but we don't do that, do we?

Also I don't see why it should impact stability or prevent from getting crashing reports from other tests?
Its that a bug on WTR or on the tooling for running tests? Its the first time I hear this. Can you elaborate on why its this a problem? Thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200227/dadc306c/attachment.htm>