165064 2016-11-24 07:31:32 -0800 ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js is failing. 2016-11-28 09:12:20 -0800 1 1 1 Unclassified WebKit JavaScriptCore WebKit Local Build Unspecified Unspecified RESOLVED DUPLICATE 162567 P2 Normal --- 1 mark.lam webkit-unassigned fpizlo ggaren jfbastien keith_miller msaboff ryanhaddad saam ysuzuki oldest_to_newest 1253586 0 mark.lam 2016-11-24 07:31:32 -0800 The ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js test changes the prototype of a constructor function and expects new instances to inherit the new prototype. However, it does not appear to succeed at doing this. Some details: 1. The issue appears to be racy. it's not easily reproducible on demand though it happens a lot on the bots, and I can reproduce it locally sometimes. 2. If I disable inlining and DFG compilation, I can't seem to reproduce it (assuming (1) above is not interfering). 3. If I disable the concurrent JIT, I can't seem to reproduce it (assuming (1) above is not interfering). 4. If I add options to dump disassembly, etc, I can't seem to reproduce it (assuming (1) above is not interfering). The failing test output: 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-11-23 22:36:32.000000000 -0800 ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: +++ ../ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default.out 2016-11-23 23:34:34.000000000 -0800 ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: @@ -2,12 +2,12 @@ ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: oa1[0]: { a: 0, b: 1, p: 100, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: oa1[1]: { a: 0, b: 1, p: 100, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: oa1[2]: { a: 0, b: 1, p: 100, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: -oa1[3]: { a: 0, b: 1, p: 200, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: -oa1[4]: { a: 0, b: 1, p: 200, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: -oa1[5]: { a: 0, b: 1, p: 200, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: -oa1[6]: { a: 0, b: 1, p: 200, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: -oa1[7]: { a: 0, b: 1, p: 200, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: -oa1[8]: { a: 0, b: 1, p: 200, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: +oa1[3]: { a: 0, b: 1, p: 100, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: +oa1[4]: { a: 0, b: 1, p: 100, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: +oa1[5]: { a: 0, b: 1, p: 100, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: +oa1[6]: { a: 0, b: 1, p: 100, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: +oa1[7]: { a: 0, b: 1, p: 100, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: +oa1[8]: { a: 0, b: 1, p: 100, x: 10, y: 11 } ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: 1253844 1 ryanhaddad 2016-11-28 09:03:29 -0800 Dupe of https://bugs.webkit.org/show_bug.cgi?id=162567? 1253845 2 mark.lam 2016-11-28 09:12:20 -0800 *** This bug has been marked as a duplicate of bug 162567 ***