Travis builds for 2.13.0 fail
See original GitHub issueThis is something to investigate for latest master
:
- ! in Travis
2.13.0
fail with the error message pasted below - OK
2.13.1
works fine in Travis
Local behavior is the same.
Error message:
[info] com.sksamuel.scapegoat.FeedbackTest *** ABORTED ***
[info] java.lang.NoSuchMethodError: scala.tools.nsc.reporters.StoreReporter.ERROR()Lscala/reflect/internal/Reporter$Severity;
[info] at com.sksamuel.scapegoat.FeedbackTest.$anonfun$new$3(FeedbackTest.scala:30)
[info] at org.scalatest.OutcomeOf.outcomeOf(OutcomeOf.scala:85)
[info] at org.scalatest.OutcomeOf.outcomeOf$(OutcomeOf.scala:83)
[info] at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)
[info] at org.scalatest.Transformer.apply(Transformer.scala:22)
[info] at org.scalatest.Transformer.apply(Transformer.scala:20)
[info] at org.scalatest.freespec.AnyFreeSpecLike$$anon$1.apply(AnyFreeSpecLike.scala:406)
[info] at org.scalatest.TestSuite.withFixture(TestSuite.scala:196)
[info] at org.scalatest.TestSuite.withFixture$(TestSuite.scala:195)
[info] at org.scalatest.freespec.AnyFreeSpec.withFixture(AnyFreeSpec.scala:1739)
[info] ...
[error] java.lang.NoSuchMethodError: scala.tools.nsc.reporters.StoreReporter.ERROR()Lscala/reflect/internal/Reporter$Severity;
[error] at com.sksamuel.scapegoat.FeedbackTest.$anonfun$new$3(FeedbackTest.scala:30)
[error] at org.scalatest.OutcomeOf.outcomeOf(OutcomeOf.scala:85)
[error] at org.scalatest.OutcomeOf.outcomeOf$(OutcomeOf.scala:83)
[error] at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)
[error] at org.scalatest.Transformer.apply(Transformer.scala:22)
[error] at org.scalatest.Transformer.apply(Transformer.scala:20)
[error] at org.scalatest.freespec.AnyFreeSpecLike$$anon$1.apply(AnyFreeSpecLike.scala:406)
[error] at org.scalatest.TestSuite.withFixture(TestSuite.scala:196)
[error] at org.scalatest.TestSuite.withFixture$(TestSuite.scala:195)
[error] at org.scalatest.freespec.AnyFreeSpec.withFixture(AnyFreeSpec.scala:1739)
[error] at org.scalatest.freespec.AnyFreeSpecLike.invokeWithFixture$1(AnyFreeSpecLike.scala:404)
[error] at org.scalatest.freespec.AnyFreeSpecLike.$anonfun$runTest$1(AnyFreeSpecLike.scala:416)
[error] at org.scalatest.SuperEngine.runTestImpl(Engine.scala:306)
[error] at org.scalatest.freespec.AnyFreeSpecLike.runTest(AnyFreeSpecLike.scala:416)
[error] at org.scalatest.freespec.AnyFreeSpecLike.runTest$(AnyFreeSpecLike.scala:398)
[error] at com.sksamuel.scapegoat.FeedbackTest.org$scalatest$OneInstancePerTest$$super$runTest(FeedbackTest.scala:11)
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
Common Build Problems - Travis CI Docs
One possible cause for builds failing unexpectedly can be calling set -e (also known as set errexit ), either directly in your .travis.yml...
Read more >Tests passing: Build fails · Issue #7986 · travis-ci ... - GitHub
So I'm trying to use travis in my Angular 4 projet, all tests are passing but the build fails becuase "No output has...
Read more >Travis CI error while devtools::chech() doesn't - Stack Overflow
I would seem that your package depends, at least, on raster and sf ; and your script does not install them: 1: In...
Read more >react-scripts-ts-build-optimised - npm
Since 2.13.0 , typescript is listed as a peer dependency of react-scripts-ts . For projects generated with at least this version, the init ......
Read more >Log4j – Changes - Apache Logging Services
2.13.0, 2019-12-11, GA Release 2.13.0. 2.12.1, 2019-08-06 ... Fix build error in Java 9 when compiling log4j-core test classes.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Sorry for the confusion @mccartney, I haven’t really checked and for some reason I assumed it wasn’t published for 2.13 🤔
It sounds sensible to disable coursier for now until this issue gets resolved. It would be worth reporting upstream. I’ve come across a few similar issues before, I’m sure there’s already one tracking this 😃
Also, there is this bug: https://github.com/coursier/coursier/issues/1382 which causes test dependencies to be used for publishing. Which would probably mean that even if you could work around the problem in the test here, it would probably just fail at runtime for 2.13.0 everywhere else.