Skip to content

[nomerge][2.12] Welcome back Partest!#9169

Merged
dwijnand merged 3 commits intoscala:2.12.xfrom
dwijnand:2.12/wb-partest
Aug 25, 2020
Merged

[nomerge][2.12] Welcome back Partest!#9169
dwijnand merged 3 commits intoscala:2.12.xfrom
dwijnand:2.12/wb-partest

Conversation

@dwijnand
Copy link
Copy Markdown
Member

The motivation is to bring "/* scalac: ... */" pragma support to 2.12.x's partest, as easily as possible, as backporting/forward-merging changes is frequently impacted by 2.12's lack of pragma support and 2.13's lack of flags-file support...

So, as an alternative to scala/scala-partest#118, here's a without-history c+p of 2.13.x's partest, for the 2.12.x branch.

I decided to defer backporting the "testkit" split out and other related build tweaks that followed partest's re-integration into the 2.13.x branch (though I might've copied some details), particularly I had been looking at:

I also decided to defer both migrating all the flags files to pragmas as well as dropping flags support (which I actually had to restore - all the other post-copy tweaks were just mechanical changes, like scala.util.chaining and JavaConverters.)

I've tried to make a reasonable attempt at putting together a workable change, without sinking too much time into this.

But feedback welcome, particular by @som-snytt. Specifically could you check the ExtConsoleReporter/DirectCompiler close/finish/hasError logic, please?

@dwijnand

This comment has been minimized.

@som-snytt
Copy link
Copy Markdown
Contributor

It's quite some pandemic busy work. I'm surprised there is any forward merging to 2.13, and I would be surprised if partest maintenance is worth the efforts. OTOH, repairing the Vulpix split might make maintenance easier for 2.13/3.0. I have tinkered with dotty but I've forgotten again how to run a test.

@SethTisue SethTisue added the internal not resulting in user-visible changes (build changes, tests, internal cleanups) label Aug 15, 2020
@SethTisue
Copy link
Copy Markdown
Member

@sjrd will this affect Scala.js?

@sjrd
Copy link
Copy Markdown
Member

sjrd commented Aug 15, 2020

It probably will, yes. But we're used to juggling with different versions of partest depending on the version of Scala, so nothing disruptive I think.

@som-snytt
Copy link
Copy Markdown
Contributor

I might have to comment on the youtube video, Anyone else here because of Welcome Back, Partest?

By coincidence, recently I've punned on Kotter when working in Kotlin.

Copy link
Copy Markdown
Member

@lrytz lrytz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

I'm surprised there is any forward merging to 2.13

We got bitten a few times by the mismatch. At least flags are not silently ignored in 2.13, but for backports the situation is still unsafe (/* scalac: -Werror */ is silently ignored). And migrating between the two formats is really annoying.

@som-snytt
Copy link
Copy Markdown
Contributor

I'm surprised there is any backporting to 2.12, but I can see how that would be annoying.

I'll look into a Scalafix for partests!

Copy link
Copy Markdown
Member

@retronym retronym left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm happy to land this as is, but as discussed lets follow up with a migration of .flags files to pragmas and removal of support of .flags files.

@dwijnand dwijnand merged commit d8f3e8b into scala:2.12.x Aug 25, 2020
@dwijnand dwijnand deleted the 2.12/wb-partest branch August 25, 2020 19:53
@SethTisue
Copy link
Copy Markdown
Member

proposal to archive the old repo: scala/scala-partest#119

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal not resulting in user-visible changes (build changes, tests, internal cleanups)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants