worker-cloneport.html fails if the platform doesn't do 50 clones while the worker thread is posting 50K ports.
The problem is that there are no real guarantees as to how many times the ports will be cloned, because the cloning happens on a completely separate process from the message posting - this test is not valid. So the actual # clones is all over the map, making this test fail sporadically on multi-process implementations (i.e. Chromium).
We should just remove this check from this test.
Created attachment 40477 [details]
Comment on attachment 40477 [details]
Clearing flags on attachment: 40477
Committed r49009: <http://trac.webkit.org/changeset/49009>
All reviewed patches have been landed. Closing bug.