Issue metadata
Sign in to add a comment
|
adjustedR0 <= adjustedR1 |
||||||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=6413676013944832 Fuzzer: mbarbella_js_mutation_layout Job Type: linux_debug_content_shell_drt Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: adjustedR0 <= adjustedR1 blink::adjustGradientRadiiForOffsetRange blink::CSSGradientValue::addStops Minimized Testcase (0.24 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94hXOhEKh8QCf5qGK2r2ACZ_nKRPfHSo0VXvPfi5IP4BBDxpQaSljLEC0VFKISmegzY_9AlCTXapV7wjnqaAr71R-NxFZGHH4Oy6yZ2DjTZxyJNnJ2oPHYqzCEY6nDn43LwkcKwbYE2cPzSVKDbFi9FOOVOiA Filer: ashejole See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jun 7 2016
I'm 99% sure this is a dupe of issue 616993 . The fix landed at r398029, and it added a new test. Looks like CF picked up the new test, but ran it against an earlier revision: r398017. This behavior doesn't make much sense, as it's guaranteed to trigger false positives whenever we land fixes with tests. @inferno can we teach CF not to look back when finding new tests?
,
Jun 9 2016
ClusterFuzz has detected this issue as fixed in range 398017:398731. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6413676013944832 Fuzzer: mbarbella_js_mutation_layout Job Type: linux_debug_content_shell_drt Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: adjustedR0 <= adjustedR1 blink::adjustGradientRadiiForOffsetRange blink::CSSGradientValue::addStops Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_debug_content_shell_drt&range=398017:398731 Minimized Testcase (0.21 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97CfuITKioCVUbalBXuT-7RIthDiiP3t9-qFFIZ0oJMt-vT3zFQD5vsz-cHFVtbxroh74ONWNdDH0swbrSUmRFv9PN-rmftStLLTJDBaEVLaA_5vKThMtB93v8j7JQfzpoOwN5aEzeHatD7bc27HStU3vz_zQ See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jun 9 2016
,
Jun 18 2016
Florin, sorry about that. The problem gets harder since sometimes lkgr can really lag behind. in Some time, lkgr will be converted to tip-of-tree green for specific builder, and then this shouldn't be a problem.
,
Jun 18 2016
No worries, just wanted to make sure you're aware of this. Thanks!
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ashej...@chromium.org
, Jun 7 2016Components: Blink>CSS Tools>Test>FindIt>CorrectResult
Labels: -Pri-1 findit-for-crash Te-Logged M-53 Pri-2
Owner: fmalita@chromium.org
Status: Assigned (was: Available)