-
Notifications
You must be signed in to change notification settings - Fork 59
ScalaTest 3.2 #1172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ScalaTest 3.2 #1172
Conversation
so far I only glanced at a few of the failures, it looked like they are running afoul of 3.2 removing deprecated stuff I'd have to look, but it's possible that some of the failed projects are actually still declaring a 3.0 dependency, but happened to be only using APIs that remained source-compatible in 3.1 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
nice
|
fs2 we currently have frozen at v2.1.0, which pureconfig downstream expects fs2 moved to newer ScalaTest starting with v2.3.0 (and at the moment the newest tag is v2.4.2) so probably the next step here would be: try moving to fs2 v2.4.2; see what breaks; if only pureconfig breaks, open an issue requesting that they upgrade (or attempt the upgrade myself if it seems easy/quick enough); if a bunch of stuff breaks, reconsider see also typelevel/fs2#1778 for background on the ScalaTest situation in the fs2 repo oh and scalatest/scalatest#1735 (comment), sigh |
This comment has been minimized.
This comment has been minimized.
some of the failing projects declare a dependency on ScalaTest 3.0, but happened to be source-compatible with 3.1 as well, but not with 3.2. those projects can be fixed by downgrading them to 3.0, instead of moving them forward to 3.2 |
ah, I think scalamock is failing because it's getting both ScalaTest 3.0 and 3.2 on the classpath:
|
success is tantalizingly near: |
I thought adding this to + set-version: "3.2.0" // because https://github.com/tkawachi/sbt-doctest/issues/135 affects circe-config but I've never used
I'd hoped the |
for circe-config, I'm just gonna dodge the issue with:
|
the scalatest-tests thing is reproducible outside of dbuild simply by running the filename seems to vary, on second run I saw:
|
I think I'm just going to remove scalatest-tests from the build, for now anyway. perhaps I'll get some guidance over at scalatest/scalatest#1851 and/or scalatest/scalatest#1852 on what I would need to do to run the tests without all the complexity that I see in that repo's |
🎉 |
attempting to reinstate scalatest-tests: #1190 |
I don't know if this will be mergeable, but I want to at least see what happens
https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1576/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1577/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1578/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1579/SUCCEEDED: 104https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1585/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1586/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1593/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1595/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1609/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1610/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1611/SUCCEEDED: 159https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1612/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1613/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1614/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1615/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1621/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1625/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1626/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1627/SUCCEEDED: 202https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1667/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1668/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1671/SUCCEEDED: 213https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1674/SUCCEEDED: 216https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1675/https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1679/