Skip to content
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

Unexpected SocketException with certain Scalatest arguments #906

Closed
max-leuthaeuser opened this issue May 27, 2019 · 3 comments
Closed

Unexpected SocketException with certain Scalatest arguments #906

max-leuthaeuser opened this issue May 27, 2019 · 3 comments
Labels
bug A defect or misbehaviour. task / test

Comments

@max-leuthaeuser
Copy link

max-leuthaeuser commented May 27, 2019

Very similar to #658, running bloop test foo fails with:

[E] Unexpected error during remote test execution: 'Socket closed'.
[E] Internal error when running tests: sbt.ForkMain$Run$RunAborted: java.net.SocketException: Broken pipe (Write failed)

when specifying certain Scalatest arguments with sbt. E.g.:

testOptions in Test := Seq(
  Tests.Argument(TestFrameworks.ScalaTest
     "-oDI", "-W", "30", "30"
   )
)

Once these testOptions are removed, bloop test foo works without any problems.

Setup:

  • scalacenter/bloop/bloop: stable 1.2.5 via Homebrew
  • sbt.version=1.2.8
  • Scala compiler version 2.12.8
  • JDK 1.8
@tkroman
Copy link
Contributor

tkroman commented May 27, 2019

@max-leuthaeuser this is fixed in master, you can clone the repo and install bloop locally by doing
sbt install
and then

bin/install.py -n $(git -C nailgun rev-parse HEAD) -c 1.1.0-M14-4 --bloop-home /path/to/home/.bloop -v 1.2.5+430-de714404

where v will be the version generated by sbt install (will be visible in logs).

@jvican jvican changed the title java.net.SocketException with certain Scalatest arguments Unexpected SocketException with certain Scalatest arguments May 27, 2019
@jvican jvican added bug A defect or misbehaviour. has fix task / test labels May 27, 2019
@jvican
Copy link
Contributor

jvican commented May 27, 2019

Indeed, this is fixed in master, thanks @tkroman for the quick answer 😄

@jvican jvican closed this as completed May 27, 2019
@max-leuthaeuser
Copy link
Author

Thanks for the quick answer and solution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A defect or misbehaviour. task / test
Projects
None yet
Development

No branches or pull requests

3 participants