commit 1d889a518010562083c1ac0bb011bb2549896922
Author: Yi Cheng <wisechengyi@gmail.com>
Date:   Fri May 8 14:55:00 2020 -0700

    Adapt to upstream scalatest change (#9707)
    
    ### Problem
    
    ScalaTestUtil tries to hydrate org.scalatest.junit.JUnitRunner. However, it turns out that class was moved to org.scalatestplus.junit.JUnitRunner, and we never caught up. Now that they've deleted the type alias for JUnitRunner, we can't upgrade our scalatest version to 3.1.x.
    
    ### Solution
    
    use `org.scalatestplus.junit.JUnitRunner` instead as the junitRunnerClass
    
    [ci skip-rust-tests]

 src/java/org/pantsbuild/tools/junit/impl/ScalaTestUtil.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

commit 891097aa870d450d9f8f4595433315e26642edb2
Author: Nora Howard <nhoward@twitter.com>
Date:   Thu Apr 30 10:09:23 2020 -0600

    [junit-runner] allow test specs to work for parameterized tests and t… (#9397)
    
    [ci skip-rust-tests]
    ### Problem
    
    When I want to run one instance of a parameterized test, or any scala test, I can't specify a spec for it on the command line for pants' test runner.
    
    ### Solution
    
    When a custom runner or the scala test runner is being used, allow the method name portion of specs to have arbitrary contents. Also, update arg splitting to use the args as they are provided rather than splitting each individual argument.
    
    ### Result
    
    Both parameterized tests and scala tests can be referred to directly by `--test-junit-test=`

 .../tools/junit/impl/ConsoleRunnerImpl.java        | 22 ++++--------------
 src/java/org/pantsbuild/tools/junit/impl/Spec.java | 27 +++++++++++++++++++++-
 .../pantsbuild/tools/junit/impl/SpecParser.java    | 13 +++++++++--
 src/java/org/pantsbuild/tools/junit/impl/Util.java | 10 ++++----
 4 files changed, 47 insertions(+), 25 deletions(-)

commit dff0d254497955c0a2d00c792e091ac1268ae61f
Author: Nora Howard <nhoward@twitter.com>
Date:   Tue Apr 14 10:55:19 2020 -0600

    [junit-runner] simplify fail fast (#9403)
    
    [ci skip-rust-tests]  # No Rust changes made.
    
    ### Problem
    
    There's certain circumstances where fail fast would print results twice.
    
    ### Solution
    
    This simplifies the interaction between that fail fast listener and the notifier and fixes the double print issue.
    
    ### Result
    
    Now now fail fast does not make additional notifier calls that aren't necessary.
    
    This change also updates the console listener behavior so that it will print out a full failure result when it encounters failures after the results have been printed instead of an unformatted stack trace.

 .../tools/junit/impl/ConsoleListener.java          |  2 +-
 .../tools/junit/impl/ConsoleRunnerImpl.java        | 35 +++++++++-------------
 2 files changed, 15 insertions(+), 22 deletions(-)