It miiiiight be a regression from r207711 "Bindings error message for missing required dictionary member should be more explicit," but maybe it's just flaky and doesn't fail often. We'll see after couple more runs of the test bot: ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: DIFF FAILURE! 30611/37492 ......... ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: --- ../.tests/ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.baseline 2016-10-22 03:39:33.256693765 -0700 30611/37492 ......... 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-22 03:46:19.294267693 -0700 30611/37492 ......... ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: @@ -13,12 +13,12 @@ 30611/37492 ......... 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 } 30611/37492 ......... 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 } 30611/37492 ......... 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 } 30611/37492 ......... 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 } 30611/37492 ......... 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 } 30611/37492 ......... 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 } 30611/37492 ......... 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 } 30611/37492 ......... 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 } 30611/37492 ......... 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 } 30611/37492 ......... 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 } 30611/37492 ......... 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 } 30611/37492 ......... 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 } 30611/37492 ......... 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 } 30611/37492 ......... 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 } 30611/37492 ......... 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 } 30611/37492 ......... ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: 30611/37492 ......... ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: Test 3: 30611/37492 ......... ChakraCore.yaml/ChakraCore/test/fieldopts/objtypespec-newobj-invalidation.1.js.default: oa3[0]: { a: 0, b: 1, p: 100, x: 10, y: 11 }
(Why is the test output have to be so difficult to parse visually?)
(In reply to comment #0) > It miiiiight be a regression from r207711 "Bindings error message for > missing required dictionary member should be more explicit," but maybe it's > just flaky and doesn't fail often. It's not a regression, it's just flaky. I doubt it's GTK-specific.
(In reply to comment #2) > (In reply to comment #0) > > It miiiiight be a regression from r207711 "Bindings error message for > > missing required dictionary member should be more explicit," but maybe it's > > just flaky and doesn't fail often. > > It's not a regression, it's just flaky. I doubt it's GTK-specific. Yes, it seems also flaky on mac port: https://build.webkit.org/builders/Apple%20Yosemite%20Release%20JSC%20%28Tests%29/builds/15315/steps/jscore-test/logs/stdio
*** This bug has been marked as a duplicate of bug 162567 ***