mirror of
https://github.com/sbt/sbt.git
synced 2026-10-06 10:03:56 +02:00
EugeneandEugene
cfba74f6ee
**Problem** When a forked test JVM exits, WorkerProxy.watch calls notifyExit right away, and on exit code 0 that completes the run. If the response reader has not consumed the rest of the stream yet, the remaining events, logs and the final response are dropped, and the build passes with failing tests unreported. Slow listeners, or several forks at once, make this likely. **Solution** Track when the response stream reaches end of input (the socket reader for Tcp/Ipc, stdout for Stdio), and have the watch thread wait for it, with a bound, before calling notifyExit. This is what sbt 1.x did by joining the acceptor thread. The new scripted test uses a listener that sleeps per event, and fails without this change. Fixes #9859 Generated-by: Claude Opus 5.5 Co-authored-by: Eugene <[email protected]>
sbt
sbt is a build tool for Scala, Java, and more.
For general documentation, see https://www.scala-sbt.org/.
sbt 2.x
This is the 2.x series of sbt. The source code of sbt is split across several GitHub repositories, including this one.
- sbt/io hosts
sbt.iomodule. - sbt/zinc hosts Zinc, an incremental compiler for Scala.
- sbt/sbt, this repository hosts modules that implement the build tool.
Other links
- Setup: Describes getting started with the latest binary release.
- FAQ: Explains how to get help and more.
- sbt/sbt-zero-seven: hosts sbt 0.7.7 and earlier versions
Issues and Pull Requests
Please read CONTRIBUTING carefully before opening a GitHub Issue or a pull request.
If you're looking for an idea for a contribution, issues labeled with good first issue or help wanted might be good starting points.
If you would like to ask questions about sbt, there's sbt channel on Scala Discord, but it would be good to gather questions on Stackoverflow.
license
See LICENSE.