toPrimitiveJitBug654983.js test sometimes fails

[ianwjhalliday]

The test test\es6\toPrimitiveJitBug654983.js has disabled since late October 2015 (marked with the fail tag) because it was occassionally failing with spurious bailout traces in its output.

Note the Symbol.toPrimitive feature is not fully implemented and may change when it is fully implemented rendering this test obsolete or irrelevant. This issue should only be investigated once work begins on the feature again.

Ported from VSO bug 5244610

The test appears to have been added to verify that bailouts no longer occur in the repro test code, but seems they are.

Further investigation is needed. The test is disabled for now.

E.g. rl output when the test fails:

3> ch.exe -DumpOnCrash -WERExceptionSupport -ExtendedErrorStackForTestHost -forceNative -off:simpleJit -bgJitDelay:0 -dynamicprofileinput:profile.dpl.UnnamedTest1438 -es6toprimitive -trace:bailout D:\164\src\test\es6\toPrimitiveJitBug654983.js >testout1177 2>&1
3>ERROR: name of output file: D:\164\src\test\es6\testout1177; size: 202; creation: Thu Oct 29 10:03:19 2015, last access: Thu Oct 29 10:03:19 2015, now: Thu Oct 29 10:03:21 2015
3>ERROR: bad output file follows ============
3>BailOut: function: foobar ( (#1.2), #3) offset: #0025 Opcode: Add_A Kind: BailOutOnImplicitCalls
3>BailOut: function: foobar ( (#1.2), #3) offset: #0025 Opcode: Add_A Kind: BailOutOnImplicitCalls
3>PASS
3>ERROR: end of bad output file ============

[tcare]

Fixed by #3110