2.13: re-enable Scala.js tests

[SethTisue]

as per d44382b

cc @sjrd

[SethTisue]

Sébastien, I'll need your guidance here, I don't understand the failures. let us know if we can answer any questions about what's changed in 2.13, and hopefully we'll meet in the middle somewhere.

[SethTisue]

I assume it will be reproducible outside of dbuild if you just use the latest 2.13 nightly. if not let me know

[sjrd]

Yes, the 2.13 nightly reproduced the bug.

This is an easy one: it's because the fix for scala/bug#10512 hasn't reached your 2.13.x branch yet, but we already have tests for it. The tests are disabled in 2.12.{0-4} and 2.13.0-M2, because those versions are known to be defective wrt. it, but "2.13.0-pre-whatever" does not qualify to exclude the test.

In fact, testSuiteJVM/test fails too, for the exact same reason (at run-time instead of link-time, obviously).

So the fix for this one is just that you forward merge 2.12.x into 2.13.x.

[SethTisue]

aha. okay, I think at our team meeting yesterday someone said they'd be doing that shortly (in the next few days)

[sjrd]

If I manually disable that test, both testSuiteJVM/test and testSuite/test succeed.

[SethTisue]

update: I merged 2.12.x onto 2.13.x, but there isn't a new nightly build yet

[SethTisue]

new nightly: 2.13.0-pre-79e5101

trying to re-enable the test suite uncovered a regression in (I think) constant-folding: scala/scala-dev#465

[SethTisue]

current status: we're on the new collections now, so scala-js has worse problems now :-)

the current config file has tests re-enabled (so I'm closing this ticket), but the run doesn't even get that far, currently.

scala-js-stubs works, which is the part downstream projects need.