Skip to content

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

Merged
merged 71 commits into from
Jul 24, 2020
Merged

ScalaTest 3.2 #1172

merged 71 commits into from
Jul 24, 2020

Conversation

SethTisue
Copy link
Member

@SethTisue SethTisue commented Jun 25, 2020

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: 104
https://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: 159
https://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: 202
https://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: 213
https://scala-ci.typesafe.com/job/scala-2.13.x-jdk11-integrate-community-build/1674/ SUCCEEDED: 216
https://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/

@SethTisue SethTisue self-assigned this Jun 25, 2020
@SethTisue
Copy link
Member Author

SethTisue commented Jun 26, 2020

SUCCEEDED: 104, but FAILURES (UNEXPECTED): discipline-scalatest,silencer,scalameta,log4s,cachecontrol,sbt-io,squants,jwt-scala,grizzled,sksamuel-exts,scalariform,perfolation,twotails,scoverage,scapegoat,scalatest-tests,scala-typed-holes,scala-swing,scala-records,pascal

BLOCKING DOWNSTREAM: discipline-scalatest (61), silencer (45), scalameta (11), log4s (9), cachecontrol (4), sbt-io (3), squants (2), jwt-scala (2), grizzled (2), sksamuel-exts (1), scalariform (1), perfolation (1)

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

@SethTisue

This comment has been minimized.

@SethTisue

This comment has been minimized.

@SethTisue
Copy link
Member Author

SethTisue commented Jul 1, 2020

nice

https://scala-ci.typesafe.com/view/scala-2.13.x/job/scala-2.13.x-jdk11-integrate-community-build/1586/console

SUCCEEDED: 142

BLOCKING DOWNSTREAM: fs2 (14), better-monadic-for (14), scalameta (11), log4s (9), paiges (8), akka-http (8), enumeratum (5), cachecontrol (4), sbt-io (3), mockito-scala (3), squants (2), sjson-new (2), jwt-scala (2), grizzled (2), sksamuel-exts (1), scalariform (1), akka-persistence-jdbc (1), perfolation (1), circe-config (1), akka-persistence-cassandra (1)

@SethTisue
Copy link
Member Author

SethTisue commented Jul 2, 2020

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

@SethTisue

This comment has been minimized.

@SethTisue
Copy link
Member Author

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

@SethTisue
Copy link
Member Author

ah, I think scalamock is failing because it's getting both ScalaTest 3.0 and 3.2 on the classpath:

sbt:newdir> show scalamockJVM/Test/dependencyClasspath
...
[info] * Attributed(/Users/tisue/community.213/newdir/.dbuild/local-repo/0/org/scalatest/scalatest/0.1.0-dbuildx844a130f65c0a2aec1f6e1bc54f290613ceb82a5/scalatest-0.1.0-dbuildx844a130f65c0a2aec1f6e1bc54f290613ceb82a5.jar)
..
[info] * Attributed(/Users/tisue/community.213/newdir/.dbuild/local-repo/0/scalacommunitybuild/scalatest/3.0.8-dbuildx5357ef16b53db397b4d7bf413e496c45c35ccaaa/scalatest-3.0.8-dbuildx5357ef16b53db397b4d7bf413e496c45c35ccaaa.jar)
...

@SethTisue
Copy link
Member Author

success is tantalizingly near: SUCCEEDED: 213; FAILURES (UNEXPECTED): circe-config,akka-persistence-jdbc,akka-management,scalatest-tests; FAILED: 4; BLOCKED, DID NOT RUN: 2

@SethTisue
Copy link
Member Author

I thought adding this to scalatest.conf might fix circe-config:

+  set-version: "3.2.0"  // because https://github.com/tkawachi/sbt-doctest/issues/135 affects circe-config

but I've never used set-version before and it didn't seem to have any effect:

[circe-config] All Dependencies for subproject default-sbt-project:
...
[circe-config]    org.scalatest:scalatest:0.1.0-dbuildx844a130f65c0a2aec1f6e1bc54f290613ceb82a5:test
...

I'd hoped the 0.1.0-dbuildx844... would be 3.2.0-dbuildx844... (or 3.2.0, I guess)

@SethTisue
Copy link
Member Author

SethTisue commented Jul 24, 2020

for circe-config, I'm just gonna dodge the issue with:

+  // (July 2020) this is a bit sad, but I don't see a way to work around
+  // https://github.com/tkawachi/sbt-doctest/issues/135
+  extra.run-tests: false

@SethTisue
Copy link
Member Author

SethTisue commented Jul 24, 2020

the scalatest-tests thing is reproducible outside of dbuild simply by running genSortedTests/test in the ScalaTest repo

the filename seems to vary, on second run I saw:

[error] (genSortedTests / Test / managedSources) java.io.FileNotFoundException: scalatest-test/src/test/scala/org/scalatest/ShouldBeSortedLogicalAndSpec.scala (No such file or directory)

@SethTisue
Copy link
Member Author

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 .travis.yml and travis_build.sh. it's complexity I can't really afford to get involved in

@SethTisue SethTisue marked this pull request as ready for review July 24, 2020 22:53
@SethTisue SethTisue merged commit 73f680e into scala:2.13.x Jul 24, 2020
@SethTisue
Copy link
Member Author

🎉

@SethTisue SethTisue deleted the scalatest-3.2 branch July 24, 2020 22:54
@SethTisue
Copy link
Member Author

attempting to reinstate scalatest-tests: #1190

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant