Re: [scala-ide-dev] pairs (scala-ide-snapshot , scala-master-snapshot) for which the tests pass

[iulian dragos]

Hi Miguel,

On Sat, May 18, 2013 at 8:26 PM, Miguel Garcia <miguelalfr...@epfl.ch> wrote:

I'm trying to using the new backend http://magarciaepfl.github.io/scala/ to build the Scala IDE (and in general other projects in the Scala ecosystem)

First of all, I've read previous posts on building the Scala IDE using Scala 2.11 as well as
  http://scala-ide.org/docs/dev/building/building.html#build-the-scala-ide-with-a-local-version-of-the-scala-compiler

The instructions are there, but it looks like not all scala-master-snapshot lead to success (well, I tried with the latest only).

Is there a way to know for which pairs (scala-ide-snapshot , scala-master-snapshot) the tests pass?

I don't know what you call "scala-master-snapshot". Scala ide master can be built with 2.11.0-SNAPSHOT (latest nightly should pass all tests).

 

Maybe a Jenkins job showing that information?

You can have a look here: https://jenkins.scala-ide.org:8496/jenkins/view/4.0.x/job/master-2.11.0-SNAPSHOT/ 

In principle, you should be able to build by running `./build.all -Pscala-2.11.x -Dscala.version=2.11.0-SNAPSHOT` (or another one, if your backend is published with a special version). However, dependencies are NOT re-built. If this one succeeds and want to check that Scala IDE dependencies also build fine, have a look at

https://github.com/scala-ide/uber-build

hope this helps,

iulian

 

Miguel
http://lampwww.epfl.ch/~magarcia/ScalaCompilerCornerReloaded/

--
You received this message because you are subscribed to the Google Groups "Scala IDE Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
« Je déteste la montagne, ça cache le paysage »
Alphonse Allais

[Miguel Garcia]

The new backend appears to be good enough for the Scala IDE. At least, most tests pass (more on this below), and an update-site is built. I'm struggling with "constraint not satisfied" configuration issues to start a new Eclipse instance with the update-site in question (things like, "2.10" expected vs. "2.11 SNAPSHOT" available).

The tests that I've disabled fall into two categories:

  (a) tests dependent on the SBT builder, the "compiler interface" offered by the new backend (which is based on 2.11) doesn't quite fit sbt expectations

  (b) tests that expect to find certain classnames (e.g., ScalaDebugSteppingTest). For example, currently the new backend emits "Late Closure Classes" with an "LCC" marker in their name, which is different from the "anonFun" traditionally used for anon-closure-classes.


It's definitely preliminary and work in progress (basically because the struggle with configuration files diminishes the wow factor) but after the above steps, build-all shows (using the new backend, at optimization level -o3)

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] org.scala-ide.sdt.build ........................... SUCCESS [0.953s]
[INFO] org.scala-ide.sdt.aspects ......................... SUCCESS [8.422s]
[INFO] org.scala-ide.sdt.core ............................ SUCCESS [51.731s]
[INFO] org.scala-ide.sdt.core.tests ...................... SUCCESS [2:17.602s]
[INFO] org.scala-ide.sdt.spy ............................. SUCCESS [6.336s]
[INFO] org.scala-ide.sdt.debug ........................... SUCCESS [18.913s]
[INFO] org.scala-ide.sdt.debug.tests ..................... SUCCESS [43.295s]
[INFO] org.scala-ide.sdt.weaving.feature ................. SUCCESS [0.228s]
[INFO] org.scala-ide.sdt.feature ......................... SUCCESS [0.274s]
[INFO] org.scala-ide.sdt.dev.feature ..................... SUCCESS [0.204s]
[INFO] org.scala-ide.sdt.source.feature .................. SUCCESS [0.357s]
[INFO] org.scala-ide.sdt.update-site ..................... SUCCESS [5.539s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5:15.617s
[INFO] Finished at: Sun May 19 23:35:14 GMT+01:00 2013
[INFO] Final Memory: 102M/1009M
[INFO] ------------------------------------------------------------------------


Miguel
http://lampwww.epfl.ch/~magarcia/ScalaCompilerCornerReloaded/

On Saturday, May 18, 2013 8:26:51 PM UTC+2, Miguel Garcia wrote:

I'm trying to using the new backend http://magarciaepfl.github.io/scala/ to build the Scala IDE (and in general other projects in the Scala ecosystem)

First of all, I've read previous posts on building the Scala IDE using Scala 2.11 as well as
  http://scala-ide.org/docs/dev/building/building.html#build-the-scala-ide-with-a-local-version-of-the-scala-compiler

The instructions are there, but it looks like not all scala-master-snapshot lead to success (well, I tried with the latest only).

Is there a way to know for which pairs (scala-ide-snapshot , scala-master-snapshot) the tests pass?

Maybe a Jenkins job showing that information?

Miguel
http://lampwww.epfl.ch/~magarcia/ScalaCompilerCornerReloaded/

[iulian dragos]

On Mon, May 20, 2013 at 3:11 PM, Miguel Garcia <miguelalfr...@epfl.ch> wrote:

The new backend appears to be good enough for the Scala IDE. At least, most tests pass (more on this below), and an update-site is built. I'm struggling with "constraint not satisfied" configuration issues to start a new Eclipse instance with the update-site in question (things like, "2.10" expected vs. "2.11 SNAPSHOT" available).

The tests that I've disabled fall into two categories:

  (a) tests dependent on the SBT builder, the "compiler interface" offered by the new backend (which is based on 2.11) doesn't quite fit sbt expectations

I imagine the new backend is not binary compatible with the 2.11 "stock" nightly. You could fix that by running the uber-build project (it builds dependencies too), so everything should "just work".

 

  (b) tests that expect to find certain classnames (e.g., ScalaDebugSteppingTest). For example, currently the new backend emits "Late Closure Classes" with an "LCC" marker in their name, which is different from the "anonFun" traditionally used for anon-closure-classes.

As long as they are easy to update, it's good.

 

It's definitely preliminary and work in progress (basically because the struggle with configuration files diminishes the wow factor) but after the above steps, build-all shows (using the new backend, at optimization level -o3)

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] org.scala-ide.sdt.build ........................... SUCCESS [0.953s]
[INFO] org.scala-ide.sdt.aspects ......................... SUCCESS [8.422s]
[INFO] org.scala-ide.sdt.core ............................ SUCCESS [51.731s]
[INFO] org.scala-ide.sdt.core.tests ...................... SUCCESS [2:17.602s]
[INFO] org.scala-ide.sdt.spy ............................. SUCCESS [6.336s]
[INFO] org.scala-ide.sdt.debug ........................... SUCCESS [18.913s]
[INFO] org.scala-ide.sdt.debug.tests ..................... SUCCESS [43.295s]
[INFO] org.scala-ide.sdt.weaving.feature ................. SUCCESS [0.228s]
[INFO] org.scala-ide.sdt.feature ......................... SUCCESS [0.274s]
[INFO] org.scala-ide.sdt.dev.feature ..................... SUCCESS [0.204s]
[INFO] org.scala-ide.sdt.source.feature .................. SUCCESS [0.357s]
[INFO] org.scala-ide.sdt.update-site ..................... SUCCESS [5.539s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5:15.617s
[INFO] Finished at: Sun May 19 23:35:14 GMT+01:00 2013
[INFO] Final Memory: 102M/1009M
[INFO] ------------------------------------------------------------------------

Cool! Your machine seems pretty fast, too ;-)

iulian

 

Miguel
http://lampwww.epfl.ch/~magarcia/ScalaCompilerCornerReloaded/

On Saturday, May 18, 2013 8:26:51 PM UTC+2, Miguel Garcia wrote:

I'm trying to using the new backend http://magarciaepfl.github.io/scala/ to build the Scala IDE (and in general other projects in the Scala ecosystem)

First of all, I've read previous posts on building the Scala IDE using Scala 2.11 as well as
  http://scala-ide.org/docs/dev/building/building.html#build-the-scala-ide-with-a-local-version-of-the-scala-compiler

The instructions are there, but it looks like not all scala-master-snapshot lead to success (well, I tried with the latest only).

Is there a way to know for which pairs (scala-ide-snapshot , scala-master-snapshot) the tests pass?

Maybe a Jenkins job showing that information?


Miguel
http://lampwww.epfl.ch/~magarcia/ScalaCompilerCornerReloaded/

--
You received this message because you are subscribed to the Google Groups "Scala IDE Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scala-ide-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.