Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cannot build Scala (2.8.x branch and trunk) under VMware #3639

Closed
scabug opened this issue Jul 5, 2010 · 6 comments
Closed

Cannot build Scala (2.8.x branch and trunk) under VMware #3639

scabug opened this issue Jul 5, 2010 · 6 comments
Labels
build

Comments

@scabug
Copy link

scabug commented Jul 5, 2010

When building Scala I got failures:

BUILD FAILED
java.lang.RuntimeException: Test suite finished with 5 cases failing:
/home/somov/workspace/Scala2.8branch/test/files/pos/t0674.scala [FAILED]
/home/somov/workspace/Scala2.8branch/test/files/pos/t1203 [FAILED]
/home/somov/workspace/Scala2.8branch/test/files/neg/bug1017.scala [FAILED]
/home/somov/workspace/Scala2.8branch/test/files/neg/bug1011.scala [FAILED]
/home/somov/workspace/Scala2.8branch/test/files/run/lazy-traits.scala [FAILED]
	at scala.Predef$$.error(Predef.scala:58)
	at scala.tools.partest.PartestTask$$$$anonfun$$f$$1$$1.apply(PartestTask.scala:260)
	at scala.tools.partest.PartestTask$$$$anonfun$$f$$1$$1.apply(PartestTask.scala:260)
	at scala.tools.partest.PartestTask.execute(PartestTask.scala:269)
	at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
	at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
	at org.apache.tools.ant.Task.perform(Task.java:348)
	at org.apache.tools.ant.Target.execute(Target.java:357)
	at org.apache.tools.ant.Target.performTasks(Target.java:385)
	at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
	at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
	at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
	at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
	at org.apache.tools.ant.Main.runBuild(Main.java:758)
	at org.apache.tools.ant.Main.startAnt(Main.java:217)
	at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
	at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)

An extract of the output is attached.

Java version

# JRE version: 6.0-b16
# Java VM: OpenJDK Client VM (14.0-b16 mixed mode, sharing linux-x86 )
# Distribution: Ubuntu 9.10, package 6b16-1.6.1-3ubuntu3

The same problem on Ubuntu 10.04 with Java build 1.6.0_20-b02. The same configuration without VMware runs without failures.

I use Scala 2.8.0RC7 under VMware and I do not experience any problems.

I do not know whether this needs to be fixed since I am only going to use official builds anyway.
@scabug
Copy link
Author

scabug commented Jul 5, 2010

Imported From: https://issues.scala-lang.org/browse/SI-3639?orig=1
Reporter: Andrey (andrey)
Attachments:

@scabug
Copy link
Author

scabug commented Jul 5, 2010

Andrey (andrey) said:
extract of the output (to fit in 256 kB)

@scabug
Copy link
Author

scabug commented Jul 5, 2010

Andrey (andrey) said:
error log

@scabug
Copy link
Author

scabug commented Jul 5, 2010

@paulp said:
This looks like a java bug in the crasher case, and insufficient stack and heap settings in the others. I'll leave this open briefly in case you would like to contest that, but otherwise I'll be closing it.

@scabug
Copy link
Author

scabug commented Jul 5, 2010

Andrey (andrey) said:
The settings are the same with or without VMware. I just run command 'ant all.clean test'

Feel free to close the ticket if you feel that fixing it will not anyhow increase the quality of the Scala build system.

@scabug
Copy link
Author

scabug commented Jul 5, 2010

@paulp said:
Replying to [comment:2 andrey]:

The settings are the same with or without VMware. I just run command 'ant all.clean test'

It can - and surely does - use more stack under vmware. It's easy to cross the threshold of failure. It wasn't a wild guess: I know those tests very well because they always turn up when people have insufficient stack.

@scabug scabug closed this as completed May 18, 2011
@scabug scabug added the build label Apr 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
build
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@scabug