Conversation
|
@retronym please check it out |
|
t7020.scala is failing — @dwijnand would that go away with a rebase? |
|
It might but not necessarily. |
|
It also fails on 2.12, so here is a backport. Pandemic code review is hard. I see I mentioned something about the forward merge colliding with my related fix. I kind of remember staring at this code, but missed the bug. Also 2 or 3 other comments came up. What about the JDK OPT to look up |
|
I was about to say I'd have to read more doc. 4.4.17 file name: (Variable) At https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT via https://www.loc.gov/preservation/digital/formats/fdd/fdd000354.shtml |
|
how come backport PR passes all the checks and this PR doesn't? should I rebase on lastest 2.13.x? |
|
I think they were saying there is a so-called flaky test on 2.13. Kind of makes you wish you had PRd against 2.12. |
|
yeah rebasing this onto current 2.13.x should fix (by pulling in #9540) |
When I tried to upgrade from Scala 2.13.2 to Scala 2.13.3-5 I started to get strange compiler error.
After some debug I figured that some of our dependency jars in the root have files which names start with
/.So I added a simple unit test that on
2.13.xfails withWhich is exactly the error I get on 2.13.3+
Looks like this was introduced in 7068589#diff-3bf883c780984a2c8f1eda1e70bb6359c4696519142992a4ee7eedf7b6887000
I didn't find a bug like this reported, but maybe it exists.