search

sbt / sbt-remote-control

Create and manage sbt process using unicorns and forks
Other
74 stars 14 forks source link

Integration tests fail #102

Open andriusj opened 10 years ago

andriusj commented 10 years ago

A clean master checkout and "sbt integration-tests" results in jansi 1.11 not being found in the repository. What gives?

[info] [IT] Running: com.typesafe.sbtrc.it.loading.CanLoadSimpleProject [IT] Running with args: java -Dsbt.boot.directory=C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\integration-test\com-typesafe-sbtrc-it-loading-CanLoadSimpleProject\boot -Dsbt.probe.trace=true -Dakka.loglevel=DEBUG -Dakka.actor.debug.autoreceive=on -Dakka.actor.debug.receive=on -Dakka.actor.debug.lifecycle=on -jar C:\work\sbt-remote-control.old\sbt-remote-control\target\sbt\sbt-launch.jar @file:/C:/work/sbt-remote-control.old/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-loading-CanLoadSimpleProject/sbt.boot.properties [info] Getting org.fusesource.jansi jansi 1.11 ... [info] [info] :: problems summary :: [info] :::: WARNINGS [info] module not found: org.fusesource.jansi#jansi;1.11 [info] [info] ==== it-local: tried [info] [info] file:/C:/work/sbt-remote-control.old/sbt-remote-control/it-runner/target/local-repository/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml [info] [info] :::::::::::::::::::::::::::::::::::::::::::::: [info] [info] :: UNRESOLVED DEPENDENCIES :: [info] [info] :::::::::::::::::::::::::::::::::::::::::::::: [info] [info] :: org.fusesource.jansi#jansi;1.11: not found [info] [info] :::::::::::::::::::::::::::::::::::::::::::::: [info] [info]

jsuereth commented 10 years ago

Looks like I may have messed up the IT test suite for windows. My guess is there's some failed space handling or URI pathing in the suite.

Any chance you can provide some more info, like what your boot.properties looks like or where your home directory is?

Thanks, and sorry. I seem to be king at breaking windows.

andriusj commented 10 years ago

It's checked out in c:/work/sbt-remote-control, so no spaces whatsoever. The complete log is [info] Loading project definition from C:\work\sbt-remote-control.old\sbt-remote-control\project [info] Set current project to root (in build file:/C:/work/sbt-remote-control.old/sbt-remote-control/) [warn] Multiple resolvers having different access mechanism configured with same name 'typesafe-ivy-private-releases'. To avoid conflict, Remove duplicate project resolvers (resolvers) or rename publishing resolver (publishTo). [info] :: delivering :: com.typesafe.sbtrc#client;1.0-fd3d55bb002017a58087151be8aac4b41dfeb017 :: 1.0-fd3d55bb002017a58087151be8aac4b41dfeb017 :: release :: Mon Apr 07 17:05:07 EEST 2014 [info] delivering ivy file to C:\work\sbt-remote-control.old\sbt-remote-control\client\target\ivy-1.0-fd3d55bb002017a58087151be8aac4b41dfeb017.xml [info] Packaging C:\work\sbt-remote-control.old\sbt-remote-control\client\target\client-1.0-fd3d55bb002017a58087151be8aac4b41dfeb017.jar ... [info] Done packaging. [info] Publishing sbt.IvySbt$Module@128cdd0c to local repo: install-to-local-project-repository [info] published client to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\client\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\jars\client.jar [info] published client to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\client\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\jars\client-tests.jar [info] published client to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\client\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\srcs\client-sources.jar [info] published ivy to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\client\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\ivys\ivy.xml [info] :: delivering :: com.typesafe.sbtrc#terminal;1.0-fd3d55bb002017a58087151be8aac4b41dfeb017 :: 1.0-fd3d55bb002017a58087151be8aac4b41dfeb017 :: release :: Mon Apr 07 17:05:07 EEST 2014 [info] delivering ivy file to C:\work\sbt-remote-control.old\sbt-remote-control\terminal\target\ivy-1.0-fd3d55bb002017a58087151be8aac4b41dfeb017.xml [info] Packaging C:\work\sbt-remote-control.old\sbt-remote-control\terminal\target\terminal-1.0-fd3d55bb002017a58087151be8aac4b41dfeb017.jar ... [info] Done packaging. [info] Publishing sbt.IvySbt$Module@387dd89b to local repo: install-to-local-project-repository [info] published terminal to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\terminal\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\jars\terminal.jar [info] published terminal to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\terminal\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\srcs\terminal-sources.jar [info] published ivy to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\terminal\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\ivys\ivy.xml [warn] Multiple resolvers having different access mechanism configured with same name 'typesafe-ivy-releases'. To avoid conflict, Remove duplicate project resolvers (resolvers) or rename publishing resolver (publishTo). [info] :: delivering :: com.typesafe.sbtrc#ui-interface-0-13;1.0-fd3d55bb002017a58087151be8aac4b41dfeb017 :: 1.0-fd3d55bb002017a58087151be8aac4b41dfeb017 :: release :: Mon Apr 07 17:05:07 EEST 2014 [info] delivering ivy file to C:\work\sbt-remote-control.old\sbt-remote-control\ui-interface\target\sbt-0.13\ivy-1.0-fd3d55bb002017a58087151be8aac4b41dfeb017.xml [info] Packaging C:\work\sbt-remote-control.old\sbt-remote-control\ui-interface\target\sbt-0.13\ui-interface-0-13-1.0-fd3d55bb002017a58087151be8aac4b41dfeb017.jar ... [info] Done packaging. [info] Publishing sbt.IvySbt$Module@593f7ede to local repo: install-to-local-project-repository [info] published ui-interface-0-13 to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\ui-interface-0-13\scala_2.10\sbt_0.13\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\jars\ui-interface-0-13.jar [info] published ui-interface-0-13 to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\ui-interface-0-13\scala_2.10\sbt_0.13\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\srcs\ui-interface-0-13-sources.jar [info] published ivy to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\ui-interface-0-13\scala_2.10\sbt_0.13\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\ivys\ivy.xml [info] :: delivering :: com.typesafe.sbtrc#server-0-13;1.0-fd3d55bb002017a58087151be8aac4b41dfeb017 :: 1.0-fd3d55bb002017a58087151be8aac4b41dfeb017 :: release :: Mon Apr 07 17:05:07 EEST 2014 [info] delivering ivy file to C:\work\sbt-remote-control.old\sbt-remote-control\server\target\ivy-1.0-fd3d55bb002017a58087151be8aac4b41dfeb017.xml [info] Publishing sbt.IvySbt$Module@16443d7f to local repo: install-to-local-project-repository [info] published server-0-13 to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\server-0-13\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\jars\server-0-13.jar [info] published server-0-13 to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\server-0-13\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\srcs\server-0-13-sources.jar [info] published ivy to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\server-0-13\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\ivys\ivy.xml [info] :: delivering :: com.typesafe.sbtrc#integration-tests;1.0-fd3d55bb002017a58087151be8aac4b41dfeb017 :: 1.0-fd3d55bb002017a58087151be8aac4b41dfeb017 :: release :: Mon Apr 07 17:05:08 EEST 2014 [info] delivering ivy file to C:\work\sbt-remote-control.old\sbt-remote-control\integration-tests\target\ivy-1.0-fd3d55bb002017a58087151be8aac4b41dfeb017.xml [info] Publishing sbt.IvySbt$Module@7a17dc90 to local repo: install-to-local-project-repository [info] published integration-tests to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\integration-tests\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\jars\integration-tests.jar [info] published integration-tests to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\integration-tests\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\srcs\integration-tests-sources.jar [info] published ivy to C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\local-art-repository\com.typesafe.sbtrc\integration-tests\1.0-fd3d55bb002017a58087151be8aac4b41dfeb017\ivys\ivy.xml [info] [IT] Running: com.typesafe.sbtrc.it.loading.CanLoadSimpleProject [IT] Running with args: java -Dsbt.boot.directory=C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\integration-test\com-typesafe-sbtrc-it-loading-CanLoadSimpleProject\boot -Dsbt.probe.trace=true -Dakka.loglevel=DEBUG -Dakka.actor.debug.autoreceive=on -Dakka.actor.debug.receive=on -Dakka.actor.debug.lifecycle=on -jar C:\work\sbt-remote-control.old\sbt-remote-control\target\sbt\sbt-launch.jar @file:/C:/work/sbt-remote-control.old/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-loading-CanLoadSimpleProject/sbt.boot.properties [info] Getting org.fusesource.jansi jansi 1.11 ... [info] [info] :: problems summary :: [info] :::: WARNINGS [info] module not found: org.fusesource.jansi#jansi;1.11 [info] [info] ==== it-local: tried [info] [info] file:/C:/work/sbt-remote-control.old/sbt-remote-control/it-runner/target/local-repository/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml [info] [info] :::::::::::::::::::::::::::::::::::::::::::::: [info] [info] :: UNRESOLVED DEPENDENCIES :: [info] [info] :::::::::::::::::::::::::::::::::::::::::::::: [info] [info] :: org.fusesource.jansi#jansi;1.11: not found [info] [info] :::::::::::::::::::::::::::::::::::::::::::::: [info] [info] [info] [info] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS [info] unresolved dependency: org.fusesource.jansi#jansi;1.11: not found [info] Error during sbt execution: Error retrieving required libraries [info](see C:worksbt-remote-control.oldsbt-remote-controlit-runnertargetintegration-testcom-typesafe-sbtrc-it-loading-CanLoadSimpleProjectbootupdate.log for complete log) [info] Error: Could not retrieve jansi 1.11 [error] [IT] com.typesafe.sbtrc.it.loading.CanLoadSimpleProject result: FAILURE [info] [IT] Running: com.typesafe.sbtrc.it.loading.CanUseUiInteractionPlugin [IT] Running with args: java -Dsbt.boot.directory=C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\integration-test\com-typesafe-sbtrc-it-loading-CanUseUiInteractionPlugin\boot -Dsbt.probe.trace=true -Dakka.loglevel=DEBUG -Dakka.actor.debug.autoreceive=on -Dakka.actor.debug.receive=on -Dakka.actor.debug.lifecycle=on -jar C:\work\sbt-remote-control.old\sbt-remote-control\target\sbt\sbt-launch.jar @file:/C:/work/sbt-remote-control.old/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-loading-CanUseUiInteractionPlugin/sbt.boot.properties [info] Getting org.fusesource.jansi jansi 1.11 ... [info] [info] :: problems summary :: [info] :::: WARNINGS [info] module not found: org.fusesource.jansi#jansi;1.11 [info] [info] ==== it-local: tried [info] [info] file:/C:/work/sbt-remote-control.old/sbt-remote-control/it-runner/target/local-repository/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml [info] [info] :::::::::::::::::::::::::::::::::::::::::::::: [info] [info] :: UNRESOLVED DEPENDENCIES :: [info] [info] :::::::::::::::::::::::::::::::::::::::::::::: [info] [info] :: org.fusesource.jansi#jansi;1.11: not found [info] [info] :::::::::::::::::::::::::::::::::::::::::::::: [info] [info] [info] [info] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS [info] unresolved dependency: org.fusesource.jansi#jansi;1.11: not found [info] Error during sbt execution: Error retrieving required libraries [info](see C:worksbt-remote-control.oldsbt-remote-controlit-runnertargetintegration-testcom-typesafe-sbtrc-it-loading-CanUseUiInteractionPluginbootupdate.log for complete log) [info] Error: Could not retrieve jansi 1.11 [error] [IT] com.typesafe.sbtrc.it.loading.CanUseUiInteractionPlugin result: FAILURE [info] --- Integration Test Report --- [info] * com.typesafe.sbtrc.it.loading.CanLoadSimpleProject [ FAILED ] see C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\integration-test\com-typesafe-sbtrc-it-loading-CanLoadSimpleProject.log [info] * com.typesafe.sbtrc.it.loading.CanUseUiInteractionPlugin [ FAILED ] see C:\work\sbt-remote-control.old\sbt-remote-control\it-runner\target\integration-test\com-typesafe-sbtrc-it-loading-CanUseUiInteractionPlugin.log java.lang.RuntimeException: Failing integration tests! at scala.sys.package$.error(package.scala:27) at integration$.handleResults(integration.scala:69) at integration$$anonfun$settings$3.apply(integration.scala:35) at integration$$anonfun$settings$3.apply(integration.scala:33) at scala.Function3$$anonfun$tupled$1.apply(Function3.scala:35) at scala.Function3$$anonfun$tupled$1.apply(Function3.scala:34) at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47) at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:42) at sbt.std.Transform$$anon$4.work(System.scala:64) at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:237) at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:237) at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:18) at sbt.Execute.work(Execute.scala:244) at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:237) at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:237) at sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:160) at sbt.CompletionService$$anon$2.call(CompletionService.scala:30) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) error Failing integration tests! [error] Total time: 2 s, completed Apr 7, 2014 5:05:09 PM

my home is C:\Users\phuqi_000

not sure where I can find my boot.properties though, is it a part of sbt or what?

jsuereth commented 10 years ago

hmm.... Which sbt launcher version are you using? If it's forcing a download of 1.11 jline, that may be a 0.12 launcher. While this shouldn't matter, I wonder if that's causing the issue....

andriusj commented 10 years ago

Downloaded a fresh 0.13.1 from http://repo.scala-sbt.org/scalasbt/sbt-native-packages/org/scala-sbt/sbt/0.13.1/sbt.zip

Extracted to c:\tools\sbt\bin\sbt integration-tests

tried to launch

C:\work\sbt-remote-control>C:\tools\sbt\bin\sbt integration-tests

Same error. Anything else I can help you with localizing the issue?

Andrius

On Mon, Apr 7, 2014 at 5:23 PM, Josh Suereth notifications@github.comwrote:

hmm.... Which sbt launcher version are you using? If it's forcing a download of 1.11 jline, that may be a 0.12 launcher. While this shouldn't matter, I wonder if that's causing the issue....

Reply to this email directly or view it on GitHubhttps://github.com/sbt/sbt-remote-control/issues/102#issuecomment-39735994 .

andriusj commented 10 years ago

The above should read, extracted to c:\tools\sbt

On Mon, Apr 7, 2014 at 6:06 PM, Andrius Juozapaitis andriusj@gmail.comwrote:

Downloaded a fresh 0.13.1 from http://repo.scala-sbt.org/scalasbt/sbt-native-packages/org/scala-sbt/sbt/0.13.1/sbt.zip

Extracted to c:\tools\sbt\bin\sbt integration-tests

tried to launch

C:\work\sbt-remote-control>C:\tools\sbt\bin\sbt integration-tests

Same error. Anything else I can help you with localizing the issue?

Andrius

On Mon, Apr 7, 2014 at 5:23 PM, Josh Suereth notifications@github.comwrote:

hmm.... Which sbt launcher version are you using? If it's forcing a download of 1.11 jline, that may be a 0.12 launcher. While this shouldn't matter, I wonder if that's causing the issue....

Reply to this email directly or view it on GitHubhttps://github.com/sbt/sbt-remote-control/issues/102#issuecomment-39735994 .

jsuereth commented 10 years ago

what does C:\tools\sbt\bin\sbt --version show?

andriusj commented 10 years ago

C:\work\sbt-remote-control>C:\tools\sbt\bin\sbt --version sbt launcher version 0.13.1

On Mon, Apr 7, 2014 at 6:07 PM, Josh Suereth notifications@github.comwrote:

what does C:\tools\sbt\bin\sbt --version show?

Reply to this email directly or view it on GitHubhttps://github.com/sbt/sbt-remote-control/issues/102#issuecomment-39742050 .

jsuereth commented 10 years ago

This is master sbt-remote-control right? I'll see if i can fix this shortly.

andriusj commented 10 years ago

correct, just git clone https://github.com/sbt/sbt-remote-control.git

On Mon, Apr 7, 2014 at 7:13 PM, Josh Suereth notifications@github.comwrote:

This is master sbt-remote-control right? I'll see if i can fix this shortly.

Reply to this email directly or view it on GitHubhttps://github.com/sbt/sbt-remote-control/issues/102#issuecomment-39750266 .

jsuereth commented 10 years ago

k, just reproduced. Will try to fix shortly.

andriusj commented 10 years ago

Any ETA when this could be fixed? I would like to integrate this new and awesome sbt remote in one of my toy projects, and integration tests seem to be a decent place to start.

jsuereth commented 10 years ago

No, things still failing on windows for me even after fixing the jline thing. I'm working on it though. On Apr 11, 2014 12:24 PM, "andriusj" notifications@github.com wrote:

Any ETA when this could be fixed? I would like to integrate this new and awesome sbt remote in one of my toy projects, and integration tests seem to be a decent place to start.

Reply to this email directly or view it on GitHubhttps://github.com/sbt/sbt-remote-control/issues/102#issuecomment-40222449 .

andriusj commented 10 years ago

Josh, with the above changes it now fails on both windows and linux with a timeout (below). Am I missing something else? I tried the clean checkout of master and ran it as sbt integration-tests

[andriusj_nortal@home ~]$ sbt --version Loading /usr/share/sbt/bin/sbt-launch-lib.bash sbt launcher version 0.13.1

[info] [IT] Running: com.typesafe.sbtrc.it.loading.CanUseUiInteractionPlugin [IT] Running with args: java -Dsbt.boot.directory=/home/andriusj_nortal/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-loading-CanUseUiInteractionPlugin/boot -Dsbt.probe.trace=true -Dakka.loglevel=DEBUG -Dakka.actor.debug.autoreceive=on -Dakka.actor.debug.receive=on -Dakka.actor.debug.lifecycle=on -jar /home/andriusj_nortal/sbt-remote-control/target/sbt/sbt-launch.jar @file:/home/andriusj_nortal/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-loading-CanUseUiInteractionPlugin/sbt.boot.properties [info] Getting com.typesafe.sbtrc integration-tests 1.0-94f627a2c7c73c05f1369ae7df1b1e8cf8f92026 ... [info] :: retrieving :: org.scala-sbt#boot-app [info] confs: [default] [info] 18 artifacts copied, 0 already retrieved (8714kB/511ms) [info] Getting Scala 2.10.3 (for integration-tests)... [info] :: retrieving :: org.scala-sbt#boot-scala [info] confs: [default] [info] 5 artifacts copied, 0 already retrieved (24447kB/670ms) [error] java.util.concurrent.TimeoutException: Futures timed out after [60 seconds] [error] at scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:219) [error] at scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:223) [error] at scala.concurrent.Await$$anonfun$result$1.apply(package.scala:107) [error] at scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scala:53) [error] at scala.concurrent.Await$.result(package.scala:107) [error] at com.typesafe.sbtrc.it.loading.CanUseUiInteractionPlugin$$anonfun$1.apply(CanUseUiInteractionPlugin.scala:66) [error] at com.typesafe.sbtrc.it.loading.CanUseUiInteractionPlugin$$anonfun$1.apply(CanUseUiInteractionPlugin.scala:40) [error] at com.typesafe.sbtrc.it.SbtClientTest$$anonfun$8.apply(SbtClientTest.scala:116) [error] at com.typesafe.sbtrc.it.SbtClientTest$$anonfun$8.apply(SbtClientTest.scala:111) [error] at com.typesafe.sbtrc.client.SimpleConnector$OpenListener$$anon$2.run(SimpleConnector.scala:140) [error] at com.typesafe.sbtrc.it.SbtClientTest$runOneThingExecutor$2$.runWhenReady(SbtClientTest.scala:109) [error] at com.typesafe.sbtrc.it.SbtClientTest$class.withSbt(SbtClientTest.scala:131) [error] at com.typesafe.sbtrc.it.loading.CanUseUiInteractionPlugin.withSbt(CanUseUiInteractionPlugin.scala:14) [error] at com.typesafe.sbtrc.it.loading.CanUseUiInteractionPlugin$delayedInit$body.apply(CanUseUiInteractionPlugin.scala:40) [error] at scala.Function0$class.apply$mcV$sp(Function0.scala:40) [error] at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12) [error] at com.typesafe.sbtrc.it.IntegrationTest$$anonfun$run$1.apply(IntegrationTest.scala:32) [error] at com.typesafe.sbtrc.it.IntegrationTest$$anonfun$run$1.apply(IntegrationTest.scala:29) [error] at com.typesafe.sbtrc.it.package$.withContextClassloader(package.scala:12) [error] at com.typesafe.sbtrc.it.IntegrationTest.run(IntegrationTest.scala:29) [error] at xsbt.boot.Launch$$anonfun$run$1.apply(Launch.scala:109) [error] at xsbt.boot.Launch$.withContextLoader(Launch.scala:129) [error] at xsbt.boot.Launch$.run(Launch.scala:109) [error] at xsbt.boot.Launch$$anonfun$apply$1.apply(Launch.scala:36) [error] at xsbt.boot.Launch$.launch(Launch.scala:117) [error] at xsbt.boot.Launch$.apply(Launch.scala:19) [error] at xsbt.boot.Boot$.runImpl(Boot.scala:44) [error] at xsbt.boot.Boot$.main(Boot.scala:20) [error] at xsbt.boot.Boot.main(Boot.scala) [info] Not executing runnable because we only run one thing: com.typesafe.sbtrc.client.SimpleConnector$OpenListener$$anon$3@3404cd16 [error] [IT] com.typesafe.sbtrc.it.loading.CanUseUiInteractionPlugin result: FAILURE [info] [IT] Running: com.typesafe.sbtrc.it.loading.CanLoadSimpleProject [IT] Running with args: java -Dsbt.boot.directory=/home/andriusj_nortal/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-loading-CanLoadSimpleProject/boot -Dsbt.probe.trace=true -Dakka.loglevel=DEBUG -Dakka.actor.debug.autoreceive=on -Dakka.actor.debug.receive=on -Dakka.actor.debug.lifecycle=on -jar /home/andriusj_nortal/sbt-remote-control/target/sbt/sbt-launch.jar @file:/home/andriusj_nortal/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-loading-CanLoadSimpleProject/sbt.boot.properties [info] Getting com.typesafe.sbtrc integration-tests 1.0-94f627a2c7c73c05f1369ae7df1b1e8cf8f92026 ... [info] :: retrieving :: org.scala-sbt#boot-app [info] confs: [default] [info] 18 artifacts copied, 0 already retrieved (8714kB/485ms) [info] Getting Scala 2.10.3 (for integration-tests)... [info] :: retrieving :: org.scala-sbt#boot-scala [info] confs: [default] [info] 5 artifacts copied, 0 already retrieved (24447kB/668ms) [error] java.lang.RuntimeException: Never got build structure. [error] at scala.sys.package$.error(package.scala:27) [error] at com.typesafe.sbtrc.it.SbtClientTest$class.waitWithError(SbtClientTest.scala:28) [error] at com.typesafe.sbtrc.it.loading.CanLoadSimpleProject.waitWithError(CanLoadSimpleProject.scala:12) [error] at com.typesafe.sbtrc.it.loading.CanLoadSimpleProject$$anonfun$1.apply(CanLoadSimpleProject.scala:35) [error] at com.typesafe.sbtrc.it.loading.CanLoadSimpleProject$$anonfun$1.apply(CanLoadSimpleProject.scala:31) [error] at com.typesafe.sbtrc.it.SbtClientTest$$anonfun$8.apply(SbtClientTest.scala:116) [error] at com.typesafe.sbtrc.it.SbtClientTest$$anonfun$8.apply(SbtClientTest.scala:111) [error] at com.typesafe.sbtrc.client.SimpleConnector$OpenListener$$anon$2.run(SimpleConnector.scala:140) [error] at com.typesafe.sbtrc.it.SbtClientTest$runOneThingExecutor$2$.runWhenReady(SbtClientTest.scala:109) [error] at com.typesafe.sbtrc.it.SbtClientTest$class.withSbt(SbtClientTest.scala:131) [error] at com.typesafe.sbtrc.it.loading.CanLoadSimpleProject.withSbt(CanLoadSimpleProject.scala:12) [error] at com.typesafe.sbtrc.it.loading.CanLoadSimpleProject$delayedInit$body.apply(CanLoadSimpleProject.scala:31) [error] at scala.Function0$class.apply$mcV$sp(Function0.scala:40) [error] at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12) [error] at com.typesafe.sbtrc.it.IntegrationTest$$anonfun$run$1.apply(IntegrationTest.scala:32) [error] at com.typesafe.sbtrc.it.IntegrationTest$$anonfun$run$1.apply(IntegrationTest.scala:29) [error] at com.typesafe.sbtrc.it.package$.withContextClassloader(package.scala:12) [error] at com.typesafe.sbtrc.it.IntegrationTest.run(IntegrationTest.scala:29) [error] at xsbt.boot.Launch$$anonfun$run$1.apply(Launch.scala:109) [error] at xsbt.boot.Launch$.withContextLoader(Launch.scala:129) [info] Not executing runnable because we only run one thing: com.typesafe.sbtrc.client.SimpleConnector$OpenListener$$anon$3@3f5f5e1d [error] at xsbt.boot.Launch$.run(Launch.scala:109) [error] at xsbt.boot.Launch$$anonfun$apply$1.apply(Launch.scala:36) [error] at xsbt.boot.Launch$.launch(Launch.scala:117) [error] at xsbt.boot.Launch$.apply(Launch.scala:19) [error] at xsbt.boot.Boot$.runImpl(Boot.scala:44) [error] at xsbt.boot.Boot$.main(Boot.scala:20) [error] at xsbt.boot.Boot.main(Boot.scala) [error] [IT] com.typesafe.sbtrc.it.loading.CanLoadSimpleProject result: FAILURE [info] [IT] Running: com.typesafe.sbtrc.it.execution.TestExecution [IT] Running with args: java -Dsbt.boot.directory=/home/andriusj_nortal/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-execution-TestExecution/boot -Dsbt.probe.trace=true -Dakka.loglevel=DEBUG -Dakka.actor.debug.autoreceive=on -Dakka.actor.debug.receive=on -Dakka.actor.debug.lifecycle=on -jar /home/andriusj_nortal/sbt-remote-control/target/sbt/sbt-launch.jar @file:/home/andriusj_nortal/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-execution-TestExecution/sbt.boot.properties [info] Getting com.typesafe.sbtrc integration-tests 1.0-94f627a2c7c73c05f1369ae7df1b1e8cf8f92026 ... [info] :: retrieving :: org.scala-sbt#boot-app [info] confs: [default] [info] 18 artifacts copied, 0 already retrieved (8714kB/442ms) [info] Getting Scala 2.10.3 (for integration-tests)... [info] :: retrieving :: org.scala-sbt#boot-scala [info] confs: [default] [info] 5 artifacts copied, 0 already retrieved (24447kB/669ms) [error] java.lang.RuntimeException: Never got build structure. [error] at scala.sys.package$.error(package.scala:27) [error] at com.typesafe.sbtrc.it.SbtClientTest$class.waitWithError(SbtClientTest.scala:28) [error] at com.typesafe.sbtrc.it.execution.TestExecution.waitWithError(TestExecution.scala:16) [error] at com.typesafe.sbtrc.it.execution.TestExecution$$anonfun$2.apply(TestExecution.scala:73) [error] at com.typesafe.sbtrc.it.execution.TestExecution$$anonfun$2.apply(TestExecution.scala:66) [error] at com.typesafe.sbtrc.it.SbtClientTest$$anonfun$8.apply(SbtClientTest.scala:116) [error] at com.typesafe.sbtrc.it.SbtClientTest$$anonfun$8.apply(SbtClientTest.scala:111) [error] at com.typesafe.sbtrc.client.SimpleConnector$OpenListener$$anon$2.run(SimpleConnector.scala:140) [error] at com.typesafe.sbtrc.it.SbtClientTest$runOneThingExecutor$2$.runWhenReady(SbtClientTest.scala:109) [error] at com.typesafe.sbtrc.it.SbtClientTest$class.withSbt(SbtClientTest.scala:131) [error] at com.typesafe.sbtrc.it.execution.TestExecution.withSbt(TestExecution.scala:16) [error] at com.typesafe.sbtrc.it.execution.TestExecution$delayedInit$body.apply(TestExecution.scala:66) [error] at scala.Function0$class.apply$mcV$sp(Function0.scala:40) [error] at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12) [error] at com.typesafe.sbtrc.it.IntegrationTest$$anonfun$run$1.apply(IntegrationTest.scala:32) [error] at com.typesafe.sbtrc.it.IntegrationTest$$anonfun$run$1.apply(IntegrationTest.scala:29) [error] at com.typesafe.sbtrc.it.package$.withContextClassloader(package.scala:12) [error] at com.typesafe.sbtrc.it.IntegrationTest.run(IntegrationTest.scala:29) [error] at xsbt.boot.Launch$$anonfun$run$1.apply(Launch.scala:109) [error] at xsbt.boot.Launch$.withContextLoader(Launch.scala:129) [error] at xsbt.boot.Launch$.run(Launch.scala:109) [error] at xsbt.boot.Launch$$anonfun$apply$1.apply(Launch.scala:36) [error] at xsbt.boot.Launch$.launch(Launch.scala:117) [error] at xsbt.boot.Launch$.apply(Launch.scala:19) [error] at xsbt.boot.Boot$.runImpl(Boot.scala:44) [error] at xsbt.boot.Boot$.main(Boot.scala:20) [error] at xsbt.boot.Boot.main(Boot.scala) [error] [IT] com.typesafe.sbtrc.it.execution.TestExecution result: FAILURE [info] [IT] Running: com.typesafe.sbtrc.it.loading.CanCancelTasks [IT] Running with args: java -Dsbt.boot.directory=/home/andriusj_nortal/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-loading-CanCancelTasks/boot -Dsbt.probe.trace=true -Dakka.loglevel=DEBUG -Dakka.actor.debug.autoreceive=on -Dakka.actor.debug.receive=on -Dakka.actor.debug.lifecycle=on -jar /home/andriusj_nortal/sbt-remote-control/target/sbt/sbt-launch.jar @file:/home/andriusj_nortal/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-loading-CanCancelTasks/sbt.boot.properties [info] Getting com.typesafe.sbtrc integration-tests 1.0-94f627a2c7c73c05f1369ae7df1b1e8cf8f92026 ... [info] :: retrieving :: org.scala-sbt#boot-app [info] confs: [default] [info] 18 artifacts copied, 0 already retrieved (8714kB/440ms) [info] Getting Scala 2.10.3 (for integration-tests)... [info] :: retrieving :: org.scala-sbt#boot-scala [info] confs: [default] [info] 5 artifacts copied, 0 already retrieved (24447kB/635ms) [error] java.util.concurrent.TimeoutException: Futures timed out after [60 seconds] [error] at scala.concurrent.impl.Promise$DefaultPromise.ready(Promise.scala:219) [error] at scala.concurrent.impl.Promise$DefaultPromise.result(Promise.scala:223) [error] at scala.concurrent.Await$$anonfun$result$1.apply(package.scala:107) [error] at scala.concurrent.BlockContext$DefaultBlockContext$.blockOn(BlockContext.scala:53) [error] at scala.concurrent.Await$.result(package.scala:107) [error] at com.typesafe.sbtrc.it.loading.CanCancelTasks$$anonfun$1.await$1(CanCancelTasks.scala:65) [error] at com.typesafe.sbtrc.it.loading.CanCancelTasks$$anonfun$1.apply(CanCancelTasks.scala:66) [error] at com.typesafe.sbtrc.it.loading.CanCancelTasks$$anonfun$1.apply(CanCancelTasks.scala:27) [error] at com.typesafe.sbtrc.it.SbtClientTest$$anonfun$8.apply(SbtClientTest.scala:116) [error] at com.typesafe.sbtrc.it.SbtClientTest$$anonfun$8.apply(SbtClientTest.scala:111) [error] at com.typesafe.sbtrc.client.SimpleConnector$OpenListener$$anon$2.run(SimpleConnector.scala:140) [error] at com.typesafe.sbtrc.it.SbtClientTest$runOneThingExecutor$2$.runWhenReady(SbtClientTest.scala:109) [error] at com.typesafe.sbtrc.it.SbtClientTest$class.withSbt(SbtClientTest.scala:131) [error] at com.typesafe.sbtrc.it.loading.CanCancelTasks.withSbt(CanCancelTasks.scala:15) [error] at com.typesafe.sbtrc.it.loading.CanCancelTasks$delayedInit$body.apply(CanCancelTasks.scala:27) [error] at scala.Function0$class.apply$mcV$sp(Function0.scala:40) [error] at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12) [error] at com.typesafe.sbtrc.it.IntegrationTest$$anonfun$run$1.apply(IntegrationTest.scala:32) [error] at com.typesafe.sbtrc.it.IntegrationTest$$anonfun$run$1.apply(IntegrationTest.scala:29) [error] at com.typesafe.sbtrc.it.package$.withContextClassloader(package.scala:12) [error] at com.typesafe.sbtrc.it.IntegrationTest.run(IntegrationTest.scala:29) [error] at xsbt.boot.Launch$$anonfun$run$1.apply(Launch.scala:109) [error] at xsbt.boot.Launch$.withContextLoader(Launch.scala:129) [error] at xsbt.boot.Launch$.run(Launch.scala:109) [error] at xsbt.boot.Launch$$anonfun$apply$1.apply(Launch.scala:36) [error] at xsbt.boot.Launch$.launch(Launch.scala:117) [error] at xsbt.boot.Launch$.apply(Launch.scala:19) [error] at xsbt.boot.Boot$.runImpl(Boot.scala:44) [error] at xsbt.boot.Boot$.main(Boot.scala:20) [error] at xsbt.boot.Boot.main(Boot.scala) [error] [IT] com.typesafe.sbtrc.it.loading.CanCancelTasks result: FAILURE [info] --- Integration Test Report --- [info] * com.typesafe.sbtrc.it.execution.TestExecution [ FAILED ] see /home/andriusj_nortal/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-execution-TestExecution.log [info] * com.typesafe.sbtrc.it.loading.CanCancelTasks [ FAILED ] see /home/andriusj_nortal/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-loading-CanCancelTasks.log [info] * com.typesafe.sbtrc.it.loading.CanLoadSimpleProject [ FAILED ] see /home/andriusj_nortal/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-loading-CanLoadSimpleProject.log [info] * com.typesafe.sbtrc.it.loading.CanUseUiInteractionPlugin [ FAILED ] see /home/andriusj_nortal/sbt-remote-control/it-runner/target/integration-test/com-typesafe-sbtrc-it-loading-CanUseUiInteractionPlugin.log java.lang.RuntimeException: Failing integration tests! at scala.sys.package$.error(package.scala:27) at integration$.handleResults(integration.scala:69) at integration$$anonfun$settings$3.apply(integration.scala:35) at integration$$anonfun$settings$3.apply(integration.scala:33) at scala.Function3$$anonfun$tupled$1.apply(Function3.scala:35) at scala.Function3$$anonfun$tupled$1.apply(Function3.scala:34) at scala.Function1$$anonfun$compose$1.apply(Function1.scala:47) at sbt.$tilde$greater$$anonfun$$u2219$1.apply(TypeFunctions.scala:42) at sbt.std.Transform$$anon$4.work(System.scala:64) at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:237) at sbt.Execute$$anonfun$submit$1$$anonfun$apply$1.apply(Execute.scala:237) at sbt.ErrorHandling$.wideConvert(ErrorHandling.scala:18) at sbt.Execute.work(Execute.scala:244) at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:237) at sbt.Execute$$anonfun$submit$1.apply(Execute.scala:237) at sbt.ConcurrentRestrictions$$anon$4$$anonfun$1.apply(ConcurrentRestrictions.scala:160) at sbt.CompletionService$$anon$2.call(CompletionService.scala:30) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) error Failing integration tests! [error] Total time: 758 s, completed Apr 13, 2014 7:34:32 AM

jsuereth commented 10 years ago

Hmm, with a clean, the integration tests pass for me on linux, but not on windows. Still working the windows issues.

jsuereth commented 10 years ago

Ok, so we actually had a deadlock in the sbt launcher which I've fixed: https://github.com/sbt/sbt/pull/1265 (yay windows process API)

Once the next milestone is out (next week), We can move to that launcher and the integration tests should start working for you :)

jsuereth commented 10 years ago

Ok integration tests pass for me with #119, so let me know how that goes or how we can help you pull in this project!

andriusj commented 10 years ago

I've set up a linux VM, and integration tests work just fine. Still having problems on win8 though: https://gist.github.com/andriusj/70dc218f64fdda253231

jsuereth commented 10 years ago

Can you try it out with current master? It also could be that windows 8 now timesout on stderr closing as well as stdout. Which version of Java?

andriusj commented 10 years ago

Tried it earlier today, kind of hard to say what is expected and what's not: tests are running for a long time, some throw exceptions but are still successful, while others just fail. Rerunning now with the latest master and will report back.

regards, Andrius

On Tue, Apr 29, 2014 at 6:48 PM, Josh Suereth notifications@github.comwrote:

Can you try it out with current master? It also could be that windows 8 now timesout on stderr closing as well as stdout. Which version of Java?

— Reply to this email directly or view it on GitHubhttps://github.com/sbt/sbt-remote-control/issues/102#issuecomment-41693712 .

andriusj commented 10 years ago

https://gist.github.com/andriusj/9c52ad207f604eb82621

2 passed, 3 failed.

On Tue, Apr 29, 2014 at 7:04 PM, Andrius Juozapaitis andriusj@gmail.comwrote:

Tried it earlier today, kind of hard to say what is expected and what's not: tests are running for a long time, some throw exceptions but are still successful, while others just fail. Rerunning now with the latest master and will report back.

regards, Andrius

On Tue, Apr 29, 2014 at 6:48 PM, Josh Suereth notifications@github.comwrote:

Can you try it out with current master? It also could be that windows 8 now timesout on stderr closing as well as stdout. Which version of Java?

— Reply to this email directly or view it on GitHubhttps://github.com/sbt/sbt-remote-control/issues/102#issuecomment-41693712 .

jsuereth commented 10 years ago

Ok, so a few notes:

  1. The "timing" based tests are failing, most likely from taking too long. I think I should probably put some timing information for server startup and see what happens. What kind of machine is the Windows 8 one? Anything about it that could lead to slow execution?
  2. The tests which don't do too much (i.e. can fit within the timeout) work, so at least we're functioning, if not quickly.
andriusj commented 10 years ago

It's a fairly recent rig, i5 haswell @ 4.2hgz, 4 cores, 16G ram, SSD, so this is not it. Runs just fine on a linux VM with half the resources.

On Tue, Apr 29, 2014 at 8:54 PM, Josh Suereth notifications@github.comwrote:

Ok, so a few notes:

1.

The "timing" based tests are failing, most likely from taking too long. I think I should probably put some timing information for server startup and see what happens. What kind of machine is the Windows 8 one? Anything about it that could lead to slow execution? 2.

The tests which don't do too much (i.e. can fit within the timeout) work, so at least we're functioning, if not quickly.

— Reply to this email directly or view it on GitHubhttps://github.com/sbt/sbt-remote-control/issues/102#issuecomment-41709334 .

jsuereth commented 10 years ago

Right, I'm worried that something about windows is making our "nice design" not so nice. Something like slow-inter-process-sockets, etc.

We are forking two processes to start up sbt. Have you tried running the terminal application? Is startup just slow, or is actually running things on a remote-controlled sbt slow? I can start more experiments on my really slow windows box

andriusj commented 10 years ago

I highly doubt there's some kind of 'inherent' windows slowness, it's not like microsoft are that micro and/or soft. Some kind of blocking I/O is much more likely. I used a older version of sbt remote control, and it gets the job done, although I didn't like the API much, and I can't say there's any difference between linux and win installations, performance wise.

Pardon my ignorance, but how do I run the terminal app? The howto's and readme's are probably out there in the parallel universe :)

On Tue, Apr 29, 2014 at 10:45 PM, Josh Suereth notifications@github.comwrote:

Right, I'm worried that something about windows is making our "nice design" not so nice. Something like slow-inter-process-sockets, etc.

We are forking two processes to start up sbt. Have you tried running the terminal application? Is startup just slow, or is actually running things on a remote-controlled sbt slow? I can start more experiments on my really slow windows box

— Reply to this email directly or view it on GitHubhttps://github.com/sbt/sbt-remote-control/issues/102#issuecomment-41722901 .

jsuereth commented 10 years ago

@andriusj No, nothign inherent in windows, mostly us doing something wrong for the windows environment that inadvertently makes it slow. Not using windows regularly means ubuntu will probably be the best OS for sbt-remote-control....

The terminal app README is a bash file hard-coded to my computer :)

kill $(ps -ef | grep java | grep load | awk '{ print $2 }')
rm -rf ~/.sbt/boot/scala-2.10.{1,2,3}/com.typesafe.sbtrc/
java -jar /home/jsuereth/projects/sbt/sbt-remote-control/target/sbt/sbt-launch.jar @/home/jsuereth/projects/sbt/sbt-remote-control/terminal/target/resource_managed/main/sbt-client.properties

I put that in an sbt project that I want to test, the run ~ publishLocal on the sbt-remote-control project and iteratively test things. Adapted for windows, that's about it.