Test262 properties outdated

[andreabergia]

I've noticed that the test262.properties file is outdated today. The diffs are surprising though:

-     from/calling-from-valid-1-noStrict.js non-strict Spec pretty clearly says this should be undefined
+     from/calling-from-valid-1-noStrict.js {compiled-non-strict,interpreted-non-strict} Spec pretty clearly says this should be undefined

So I am not sure if just rerunning and commiting is the right fix. I guess this might be related to the optimization level of #1754 ?

[gbrail]

Yes, re-running and re-committing is the right fix, with a simple PR. However, it might be worth looking at that PR -- there is a lot of complex logic in there for calculating how to report on the test failures in the four remaining test modes (non strict, strict, interpreted, and optimized) and perhaps I missed some logic -- I think that both cases are the same, but previously we must have consolidated them into one "non-strict" case and now we don't.

[rbri]

Can we close this?

[gbrail]

I think so.

FWIW, for me, on three different OSes, even forcing Java 11 for the whole build, I can't use "updateTest262properties" without seeing a whole bunch of changes to that file that aren't relevant, so I made my last update manually. I wonder if anyone else has the same problem or if I'm doing something wrong.

[rbri]

Works for me with java 11.