Bug 163692 - Rare failure in ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default
Summary: Rare failure in ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-...
Status: RESOLVED DUPLICATE of bug 162567
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-19 13:38 PDT by Filip Pizlo
Modified: 2016-12-01 13:22 PST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Filip Pizlo 2016-10-19 13:38:19 PDT
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: DIFF FAILURE!
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: --- ../.tests/ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.baseline	2016-10-19 13:05:49.000000000 -0700
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: +++ ../ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default.out	2016-10-19 13:24:03.000000000 -0700
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: @@ -13,12 +13,12 @@
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default:  oa2[0]: { a: 0, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default:  oa2[1]: { a: 0, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default:  oa2[2]: { a: 0, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: -oa2[3]: { a: 101, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: -oa2[4]: { a: 101, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: -oa2[5]: { a: 101, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: -oa2[6]: { a: 101, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: -oa2[7]: { a: 101, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: -oa2[8]: { a: 101, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: +oa2[3]: { a: 0, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: +oa2[4]: { a: 0, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: +oa2[5]: { a: 0, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: +oa2[6]: { a: 0, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: +oa2[7]: { a: 0, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: +oa2[8]: { a: 0, b: 1, c: 2, p: 100, x: 10, y: 11 }
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default:  
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default:  Test 3:
ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default:  oa3[0]: { a: 0, b: 1, p: 100, x: 10, y: 11 }
Comment 1 Alexey Proskuryakov 2016-12-01 13:22:36 PST

*** This bug has been marked as a duplicate of bug 162567 ***