specs 1.6.0 compiled with scala 2.8.0-r18718 available for trial

[etorreborre]

Hi all,

Please have a look at this version of specs if you're using
scala-2.8.0 and let me know if it is working ok for you: http://bit.ly/MAY1x.

Note that you will need to use the scalacheck jar compiled with the
same version of scala if you use ScalaCheck functionalities.

Eric.

[ijuma]

Hey Eric,

On Sep 26, 1:28 am, etorreborre <etorrebo...@gmail.com> wrote:
> Please have a look at this version of specs if you're using
> scala-2.8.0 and let me know if it is working ok for you:http://bit.ly/MAY1x.

Thanks. It seems like there have been some changes in Scala's trunk
since then that cause issues when using this build. I tried to compile
trunk of specs with trunk of Scala and get:

http://pastebin.com/m1d5458b8

Have you been able to compile specs with a more recent version of
Scala?

Best,
Ismael

[etorreborre]

Hi Ismael,

No unfortunately I had this issue too. Actually the only way I could
get specs to compile once with scala 2.8 was to compile it with a
specific version of the eclipse plugin. Even using Maven didn't work.

I remember that it was difficult for me to reduce bugs to something
small enough to create a Trac ticket. So eventually I changed a few
constructs and was able to get a version compiling. Now there is this
other compiler bug, but again I don't know where to start to reduce
it.

I'll keep you updated of my progress.

Eric.

[ijuma]

Hi Eric,

On Oct 30, 7:20 am, etorreborre <etorrebo...@gmail.com> wrote:
> No unfortunately I had this issue too. Actually the only way I could
> get specs to compile once with scala 2.8 was to compile it with a
> specific version of the eclipse plugin. Even using Maven didn't work.

I see.

> I remember that it was difficult for me to reduce bugs to something
> small enough to create a Trac ticket. So eventually I changed a few
> constructs and was able to get a version compiling. Now there is this
> other compiler bug, but again I don't know where to start to reduce
> it.

Sounds painful. By the way, they intend to have an initial internal[1]
release of 2.8.0 in the next week of two. The aim of this release is
to test various Scala libraries and applications like specs, lift,
ScalaTest, scalacheck, etc. The plan is to then release the first beta
for 2.8.0 a few weeks after that. It would be nice to have specs
compiling for the initial release to allow some testing, which in turn
could uncover subtler bugs.

> I'll keep you updated of my progress.

Thanks!

Best,
Ismael

[1] As I understand it, this just means that it won't be widely
publicised.

[etorreborre]

> Sounds painful. By the way, they intend to have an initial internal[1]
> release of 2.8.0 in the next week of two. The aim of this release is
> to test various Scala libraries and applications like specs, lift,
> ScalaTest, scalacheck, etc

Not to offload my own work on others, but do you think that someone
from the EPFL could have a look at the current compilation error I
have if I can't find a way to reduce it?

[ijuma]

Good question. I don't know. :) It's not something they do often, but
if you can't reduce it to a small test case, it may be possible to
find the revision where the regression occurred since the code
compiled with a 2.8.0 build not long ago, right? If you want, I could
use git bisect and see if I can narrow it down.

Ismael

[ijuma]

Hi Eric,

Someone seems to have done the heavy work of reducing the problem to a
small testcase. :) See:

https://lampsvn.epfl.ch/trac/scala/ticket/2587

Best,
Ismael

[etorreborre]

Great, "Akshaal" clearly deserves a free beer from me whenever we
meet!

Eric.

[braver]

Now that that ticket is closed and ScalaCheck compiles under the
trunk, we hold our breath for the 2.8 Specs party!

Cheers,
Alexy

[etorreborre]

It's almost ready, I'm just waiting on ScalaTest to be upgraded which
should happen very soon.

[etorreborre]

Hi all,

Thanks to the EPFL team, Rickard Nilsson, Bill Venners and Mark
Harrah, all those people specs depend on ;-), there is now a 2.8.0-
Beta1-RC1 version of specs:

http://nexus.scala-tools.org/content/repositories/releases/org/scala-tools/testing/specs/1.6.1-2.8.0.Beta1-RC1/

I still have lots of small things to fix but hopefully it will work
for the simplest specs.

Eric.

[David Pollak]

Somehow the jar files had a double -RC1 tacked onto the name. I
manually fixed stuff on the filesystem (and waiting for propagation).

On Nov 19, 5:59 am, etorreborre <etorrebo...@gmail.com> wrote:
> Hi all,
>
> Thanks to the EPFL team, Rickard Nilsson, Bill Venners and Mark
> Harrah, all those people specs depend on ;-), there is now a 2.8.0-
> Beta1-RC1 version of specs:
>

> http://nexus.scala-tools.org/content/repositories/releases/org/scala-...

[Eric Torreborre]

Thanks David for that, it was a bit late when I deployed the jar yesterday,...

I'll try to be vigilant when deploying the next version, soon I hope.
 

----------------------------------------------
Eric TORREBORRE
T +61 411 707 402
E etorr...@yahoo.com
B http://etorreborre.blogspot.com
P http://specs.googlecode.com
----------------------------------------------

---

De : David Pollak <feeder.of...@gmail.com>
À : specs-users <specs...@googlegroups.com>
Envoyé le : Ven 20 Novembre 2009, 6 h 12 min 01 s
Objet : [specs-users] Re: specs 1.6.0 compiled with scala 2.8.0-r18718 available for trial

--

You received this message because you are subscribed to the Google Groups "specs-users" group.
To post to this group, send email to specs...@googlegroups.com.
To unsubscribe from this group, send email to specs-users+unsub...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/specs-users?hl=.

[ijuma]

Hi Eric,

On Nov 19, 1:59 pm, etorreborre <etorrebo...@gmail.com> wrote:
> Thanks to the EPFL team, Rickard Nilsson, Bill Venners and Mark
> Harrah, all those people specs depend on ;-), there is now a 2.8.0-
> Beta1-RC1 version of specs:

And thanks to you too. :)

> I still have lots of small things to fix but hopefully it will work
> for the simplest specs.

I tried this with a branch of configgy for 2.8.0 and the tests don't
seem to run at all from the command-line. It seems like it uses (I'm
not the author, I just ported it to 2.8.0):

object TestRunner extends SpecsFileRunner("src/test/scala/**/*.scala",
".*",
System.getProperty("system", ".*"), System.getProperty("example",
".*"))

In case this is not a known issue and you want to test a relatively
small project, it's here:

http://github.com/ijuma/configgy/commits/scala-2.8

Best,
Ismael

[etorreborre]

It's a bit depressing. I thought I just had fixed the compilation
issues I had on specs tests and boom, a compiler exception:

java.lang.Error: no-symbol does not have owner
at scala.tools.nsc.symtab.Symbols$NoSymbol$.owner
(Symbols.scala:2027)
at scala.tools.nsc.symtab.Types$Type.memberType(Types.scala:
528)
at scala.tools.nsc.typechecker.RefChecks$RefCheckTransformer$
$anonfun$addVarargBridges$1$$anonfun$5.apply(RefChecks.scala:144)
at scala.tools.nsc.typechecker.RefChecks$RefCheckTransformer$
$anonfun$addVarargBridges$1$$anonfun$5.apply(RefChecks.scala:144)
at scala.tools.nsc.symtab.Symbols$Symbol.filter(Symbols.scala:
1082)
at scala.tools.nsc.typechecker.RefChecks$RefCheckTransformer$
$anonfun$addVarargBridges$1.apply(RefChecks.scala:143)
at scala.tools.nsc.typechecker.RefChecks$RefCheckTransformer$
$anonfun$addVarargBridges$1.apply(RefChecks.scala:140)
at scala.collection.LinearSeqLike$class.foreach
(LinearSeqLike.scala:85)
at scala.collection.immutable.List.foreach(List.scala:29)
at scala.tools.nsc.typechecker.RefChecks
$RefCheckTransformer.addVarargBridges(RefChecks.scala:140)

Anyway, I'll have a look at configgy with the current jar as it is.

E.

[ijuma]

On Nov 22, 1:06 am, etorreborre <etorrebo...@gmail.com> wrote:
> It's a bit depressing. I thought I just had fixed the compilation
> issues I had on specs tests and boom, a compiler exception:

There have been quite a few fixes since the beta candidate, have you
tried with trunk?

Ismael

[etorreborre]

Hi Ismael,

I have tried to run the specifications of your configgy branch and
running the TestRunner object indeed yields nothing. However running
individuals specifications seems to be ok (there are failures and
errors apparently).

I'm going to try the latest scala-nightly and if I get the same crash
I'll start reducing it.

Eric.

[ijuma]

On Nov 23, 9:55 am, etorreborre <etorrebo...@gmail.com> wrote:
> Hi Ismael,
>
> I have tried to run the specifications of your configgy branch and
> running the TestRunner object indeed yields nothing. However running
> individuals specifications seems to be ok (there are failures and
> errors apparently).

Thanks, Eric. That's useful to know.

> I'm going to try the latest scala-nightly and if I get the same crash
> I'll start reducing it.

Good luck!

Best,
Ismael

[braver]

Apparently running the Beta1-RC1-compiled Specs suffices for testing
2.8.0-SNAPSHOT-compiled stuff for now! github.com/alaz/mongo-scala-
driver uses Specs and passes all the tests fine both under 2.7.7 and
2.8.0.Beta1-RC1 and now also 2.8.0-SNAPSHOT. So while the quirks are
being worked out, we can develop under trunk and test in Specs!

Cheers,
Alexy

[etorreborre]

Hi all,

There is a new specs release for scala 2.8.0.Beta1-RC2:

http://nexus.scala-tools.org/content/repositories/releases/org/scala-tools/testing/specs/1.6.1-2.8.0.Beta1-RC2

Note however that I still have some failing specifications that I need
to have a look at in the next days.

Eric.

[ijuma]

On Nov 29, 11:52 pm, etorreborre <etorrebo...@gmail.com> wrote:
> There is a new specs release for scala 2.8.0.Beta1-RC2:

Thanks! I updated the 2.8 branch of configgy to use this and:

- Running individual specifications seems to be OK.
- I had to exclude the scalatest transitive dependency as it was
breaking the build.
- Running the TestRunner still yields nothing.

> Note however that I still have some failing specifications that I need
> to have a look at in the next days.

Good luck. :)

Best,
Ismael

[etorreborre]

Hi Ismael,

I think I have fixed the specs file runner bug (one of my failing
tests).

Can you please try the latest version (http://nexus.scala-tools.org/
content/repositories/releases/org/scala-tools/testing/specs/
1.6.1-2.8.0.Beta1-RC2) on configgy for 2.8?

Thanks,

Eric.

[ijuma]

On Nov 30, 12:14 pm, etorreborre <etorrebo...@gmail.com> wrote:
> I think I have fixed the specs file runner bug (one of my failing
> tests).

Great. :)

> Can you please try the latest version (http://nexus.scala-tools.org/
> content/repositories/releases/org/scala-tools/testing/specs/
> 1.6.1-2.8.0.Beta1-RC2) on configgy for 2.8?

Sure. The tests now run. :)

There are 7 failures, but I haven't had a chance to investigate who is
at fault yet (configgy, specs or scala).

Best,
Ismael