Re: [GUMP@brutus]: ant/test-ant failed
On Wed, 11 Aug 2004, Steve Loughran <[EMAIL PROTECTED]> wrote: > More likely we are passing something in on the command line it > doesnt like -or the source or path is unsupported. Absolutely not: testCSC-Mono: [csc] working from source directory /home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional [csc] /home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/example.cs is out of date [csc] /home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/example2.cs is out of date [csc] compiling 2 files Executing 'mcs' with arguments: '/nologo' '/debug+' '/optimize-' '/out:/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/build/ExampleCsc.exe' '/target:exe' '/nostdlib-' '/warn:3' '/fullpaths' '/incremental-' '/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/example2.cs' '/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/example.cs' The ' characters around the executable and arguments are not part of the command. [csc] Compilation succeeded [csc] Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object [csc] ** ERROR **: file critical-sections.c: line 89 (DeleteCriticalSection): assertion failed: (ret == 0) [csc] aborting... BUILD FAILED /home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet.xml:155: csc returned: 129 ExampleCsc.exe has been created by mcs and I can even run it [EMAIL PROTECTED]:~/repo/cvs/asf/ant$ mono src/etc/testcases/taskdefs/optional/dotnet/build/ExampleCsc.exe hello, I look like Java, but I'm really .NET Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: ant/test-ant failed
Adam R. B. Jack wrote: [csc] ** ERROR **: file critical-sections.c: line 89 (DeleteCriticalSection): assertion failed: (ret == 0) [csc] aborting... BUILD FAILED /home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet.xml:155: csc returned: 129 at org.apache.tools.ant.taskdefs.optional.dotnet.NetCommand.runCommand(NetCommand.java:293) This looks fine from the Ant side and seems to be an issue with the Mono installation (as expected). Compilation succeeds but mono (the VM running the compiler) fails with an error I've never seen before. Wild-arsed guess, but I wonder if Brutus' two CPUs have something to do with this. I have two real, two HT and dont encounter it. top - 17:03:32 up 9 days, 4:50, 9 users, load average: 0.13, 0.43, 0.33 Tasks: 144 total, 2 running, 142 sleeping, 0 stopped, 0 zombie Cpu0 : 3.7% us, 2.0% sy, 0.0% ni, 94.0% id, 0.0% wa, 0.3% hi, 0.0% si Cpu1 : 3.3% us, 1.3% sy, 0.0% ni, 95.0% id, 0.0% wa, 0.3% hi, 0.0% si Cpu2 : 2.6% us, 1.0% sy, 0.0% ni, 96.4% id, 0.0% wa, 0.0% hi, 0.0% si Cpu3 : 0.7% us, 0.7% sy, 0.0% ni, 98.7% id, 0.0% wa, 0.0% hi, 0.0% si Mem: 2075000k total, 2058560k used,16440k free,95528k buffers Swap: 2096472k total,8k used, 2096464k free, 1208892k cached More likely we are passing something in on the command line it doesnt like -or the source or path is unsupported. Do we already have a Mono 1.0.1 available for Debian? I've forwarded the output/error to the Mono Debian list. If that goes nowhere I'll try to report to any Mono list. Doing a Google I see a few folks have posted this type of problem (on various versions) but I think it might be a side-effect of abnormal termination. A bug yes, but a bug due to an earlier seemingly unrelated failure. Any way to run this with more debug, or more information? Is there a simpler test we can run? Can we work on a regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: ant/test-ant failed
Wild-arsed guess, but I wonder if Brutus' two CPUs have something to do with this. Possible, I vaguely recall that brutus was running a non-standard kernel as well. BTW: Leo just updated Mono from 1.0-3 to 1.0-4 on Brutus. I think the kernel is 'testing', but I don't think it is any more non-standard than that (although I do recall something about Thom doing something, perhaps for the two CPUs). Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: ant/test-ant failed
On Wed, 11 Aug 2004, Adam R. B. Jack <[EMAIL PROTECTED]> wrote: > Wild-arsed guess, but I wonder if Brutus' two CPUs have something to > do with this. Possible, I vaguely recall that brutus was running a non-standard kernel as well. > Is there a simpler test we can run? This is really just invoking the compiler on a single source file, there isn't much that would be easier and meaningful at the same time. > Can we work on a to start with and work up? Try to check out NAnt and build it using its Makefile. This will do a lot more than Ant's test and I know I've had problems with it on my Mac when Ant's tests worked well. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: ant/test-ant failed
[csc] ** ERROR **: file critical-sections.c: line 89 (DeleteCriticalSection): assertion failed: (ret == 0) [csc] aborting... BUILD FAILED /home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet.xml:155: csc returned: 129 at org.apache.tools.ant.taskdefs.optional.dotnet.NetCommand.runCommand(NetCommand.java:293) This looks fine from the Ant side and seems to be an issue with the Mono installation (as expected). Compilation succeeds but mono (the VM running the compiler) fails with an error I've never seen before. Wild-arsed guess, but I wonder if Brutus' two CPUs have something to do with this. Do we already have a Mono 1.0.1 available for Debian? I've forwarded the output/error to the Mono Debian list. If that goes nowhere I'll try to report to any Mono list. Doing a Google I see a few folks have posted this type of problem (on various versions) but I think it might be a side-effect of abnormal termination. A bug yes, but a bug due to an earlier seemingly unrelated failure. Any way to run this with more debug, or more information? Is there a simpler test we can run? Can we work on a regards, Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: ant/test-ant failed
Stefan Bodewig wrote: On Mon, 9 Aug 2004, Adam R. B. Jack <[EMAIL PROTECTED]> wrote: So, how do we get more details so we can debug this? Run the Ant targets the test would run in verbose or debug mode directly. I.e. ant -f src/etc/testcases/taskdefs/optional/dotnet.xml testCSC -v or something like this. I'd love to help (since I know it works for me with a self-compiled Mono 1.0 on RedHat 7.x and a binary Mono 1.0 on MacOS X, so it must be something minor), but I'm currently almost unavailable for personal reasons. I'll try to free some time. The test just failed on mine because I also had baggage from the (manual) runs of ; there were .CS source files in the implicit search path that also included the .cs files in wsdltodotnet/build . I have just tuned and committed the dotnet.xml files, but for anyone running the tests automated-style (with the test teardown targets being called), the problem I encountered should not have arisen. Just checked in a fix for the rmi test too. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: ant/test-ant failed
On Tue, 10 Aug 2004, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> ant -f src/etc/testcases/taskdefs/optional/dotnet.xml testCSC -v
probe_for_apps:
Property ${env.Path} has not been set
[available] Found: ilasm in /usr/bin
[echo] ilasm.found=true
Property ${env.Path} has not been set
[available] Unable to find csc
[available] Unable to find csc.exe
[available] Unable to find csc.exe
Property ${csc.found} has not been set
[echo] csc.found=${csc.found}
Property ${env.Path} has not been set
[available] Unable to find vbc
[available] Unable to find vbc.exe
[available] Unable to find vbc.exe
Property ${vbc.found} has not been set
[echo] vbc.found=${vbc.found}
Property ${env.Path} has not been set
[available] Unable to find vjc
[available] Unable to find vjc.exe
[available] Unable to find vjc.exe
Property ${jsharp.found} has not been set
[echo] jsharp.found=${jsharp.found}
[available] Found: mcs in /usr/bin
[echo] mcs.found=true
[available] Found: ilasm in /usr/bin
[echo] mono.ilasm.found=true
Property ${env.Path} has not been set
[available] Unable to find ildasm
[available] Unable to find ildasm.exe
[available] Unable to find ildasm.exe
Property ${ildasm.found} has not been set
[echo] ildasm.found=${ildasm.found}
[echo] dotnetapps.found=true
[available] Found: mono in /usr/bin
Override ignored for property mono.executable
init:
[mkdir] Created dir:
/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/build
validate_csc:
testCSC-Mono:
[csc] working from source directory
/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional
[csc]
/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/example.cs
is out of date
[csc]
/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/example2.cs
is out of date
[csc] compiling 2 files
Executing 'mcs' with arguments:
'/nologo'
'/debug+'
'/optimize-'
'/out:/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/build/ExampleCsc.exe'
'/target:exe'
'/nostdlib-'
'/warn:3'
'/fullpaths'
'/incremental-'
'/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/example2.cs'
'/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet/example.cs'
The ' characters around the executable and arguments are
not part of the command.
[csc] Compilation succeeded
[csc] Unhandled Exception: System.NullReferenceException: Object
reference not set to an instance of an object
[csc] ** ERROR **: file critical-sections.c: line 89
(DeleteCriticalSection): assertion failed: (ret == 0)
[csc] aborting...
BUILD FAILED
/home/bodewig/repo/cvs/asf/ant/src/etc/testcases/taskdefs/optional/dotnet.xml:155:
csc returned: 129
at
org.apache.tools.ant.taskdefs.optional.dotnet.NetCommand.runCommand(NetCommand.java:293)
This looks fine from the Ant side and seems to be an issue with the
Mono installation (as expected). Compilation succeeds but mono (the
VM running the compiler) fails with an error I've never seen before.
Do we already have a Mono 1.0.1 available for Debian?
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: ant/test-ant failed
On Mon, 9 Aug 2004, Adam R. B. Jack <[EMAIL PROTECTED]> wrote: > So, how do we get more details so we can debug this? Run the Ant targets the test would run in verbose or debug mode directly. I.e. ant -f src/etc/testcases/taskdefs/optional/dotnet.xml testCSC -v or something like this. I'd love to help (since I know it works for me with a self-compiled Mono 1.0 on RedHat 7.x and a binary Mono 1.0 on MacOS X, so it must be something minor), but I'm currently almost unavailable for personal reasons. I'll try to free some time. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: ant/test-ant failed
On Mon, 9 Aug 2004, Steve Loughran wrote: we are back to CSC failing: [junit] Testcase: testCSC(org.apache.tools.ant.taskdefs.optional.DotnetTest): Caused an ERROR [junit] csc returned: 129 [junit] /usr/local/gump/public/workspace/ant/src/etc/testcases/taskdefs/optional/dotnet.xml:155: csc returned: 129 I do not beleive it went away (Gump was unfortunately taking an unscheduled vacation ;-). So, how do we get more details so we can debug this? regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: ant/test-ant failed
Gump Integration Build wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact folk at [EMAIL PROTECTED] Project test-ant has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 3 runs. Project State : 'Failed', Reason 'Build Failed' The following are affected: - test-ant : Java based build tool we are back to CSC failing: [junit] Testcase: testCSC(org.apache.tools.ant.taskdefs.optional.DotnetTest): Caused an ERROR [junit] csc returned: 129 [junit] /usr/local/gump/public/workspace/ant/src/etc/testcases/taskdefs/optional/dotnet.xml:155: csc returned: 129 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: ant/test-ant failed
On Wed, 4 Aug 2004, Stefan Bodewig wrote: These are the .NET tasks failing (brutus now has Mono installed). Since I'm unsure whether this is a glitch with the Mono install, let's wait for the next Gump run before we proceed. So Ant is using a summary print for tests, not fully reports? If it were the latter we could have Gump display them (and/or read them ourselves). Mind you, this seems the sort of thing we'd like to get real hands on. I'd like to set up a gump 'test' flavour that we use for command line testing of things like this. I'm game to work to make that happen, if it helps. regards Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: ant/test-ant failed
Gump Integration Build wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact folk at [EMAIL PROTECTED] Project test-ant has an issue affecting its community integration. This issue affects 1 projects. Project State : 'Failed', Reason 'Build Failed' The following are affected: - test-ant : Java based build tool [junit] Testcase: testCSC(org.apache.tools.ant.taskdefs.optional.DotnetTest): Caused an ERROR [junit] csc returned: 129 [junit] /usr/local/gump/public/workspace/ant/src/etc/testcases/taskdefs/optional/dotnet.xml:155: csc returned: 129 [junit] at org.apache.tools.ant.taskdefs.optional.dotnet.NetCommand.runCommand(NetCommand.java:293) [junit] at org.apache.tools.ant.taskdefs.optional.dotnet.DotnetBaseMatchingTask.addFilesAndExecute(DotnetBaseMatchingTask.java:170) [junit] at org.apache.tools.ant.taskdefs.optional.dotnet.DotnetCompile.execute(DotnetCompile.java:805) oh my. Do we by any chance have something resembling mono running on brutus? If so, I wonder if the 129 response is that platform's version of '-1', the way hpux likes to return 255. if not, is there something else on that system that goes by the name of 'csc'. If we do have mono on board, it would be very cool indeed... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: ant/test-ant failed
These are the .NET tasks failing (brutus now has Mono installed). Since I'm unsure whether this is a glitch with the Mono install, let's wait for the next Gump run before we proceed. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [GUMP@brutus]: ant/test-ant failed
On Fri, 28 May 2004, Jan Materne <[EMAIL PROTECTED]> wrote: > I can´t see anything ... Neither can I. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [GUMP@brutus]: ant/test-ant failed
I can´t see anything ... besides the last message "build success" ... Can anybody else find the error? Jan > -Original Message- > From: Gump Integration Build [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 27, 2004 9:42 PM > To: [EMAIL PROTECTED] > Subject: [EMAIL PROTECTED]: ant/test-ant failed > > > To whom it may engage... > > This is an automated request, but not an unsolicited one. For > more information please visit http://gump.apache.org/nagged.html, > and/or contact folk at [EMAIL PROTECTED] > > Project test-ant has an issue affecting its community integration. > Project State : 'Failed', Reason 'Build Failed' > > Full details are available at: > > http://brutus.apache.org:8080/gump/ant/test-ant/index.html > > That said, some snippets follow: > > > The following annotations were provided: > -INFO- Failed with reason build failed > -INFO- Enable "debug" output, due to build failure. > > > The following work was performed: > http://brutus.apache.org:8080/gump/ant/test-ant/gump_work/buil > d_ant_test-ant.html > Work Name: build_ant_test-ant (Type: Build) > State: Failed > Elapsed: 0 hours, 6 minutes, 5 seconds > Command Line: java -Djava.awt.headless=true > -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-xerces2 /java/build/xercesImpl.jar:/usr/local/gump/public/> workspace/xml-xerces2/java/build/xml-apis.jar:/usr/local/gump/ > public/workspace/xml-commons/java/external/build/xml-apis.jar: /usr/local/gump/public/workspace/xml-> xalan/java/build/xalan-unbundled.jar > org.apache.tools.ant.Main > -Dgump.merge=/usr/local/gump/public/gump/work/merge.xml > -Dbuild.sysclasspath=only -Dtest.haltonfailure=false > -Dant.home=/usr/local/gump/public/workspace/ant/dist run-tests > [Working Directory: /usr/local/gump/public/workspace/ant] > CLASSPATH : > /usr/local/j2sdk1.4.2_04/lib/tools.jar:/usr/local/gump/public/ > workspace/ant/build/testcases:/usr/local/gump/public/workspace > /ant/src/testcases:/usr/local/gump/public/workspace/ant/src/et > c/testcases:/usr/local/gump/public/workspace/ant/build/lib/ant > -stylebook.jar:/usr/local/gump/public/workspace/ant/build/lib/ > ant-swing.jar:/usr/local/gump/public/workspace/ant/build/lib/a > nt-apache-resolver.jar:/usr/local/gump/public/workspace/ant/bu > ild/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/bu > ild/lib/ant-apache-regexp.jar:/usr/local/gump/public/workspace > /ant/build/lib/ant-commons-net.jar:/usr/local/gump/public/work > space/ant/build/lib/ant-apache-log4j.jar:/usr/local/gump/publi > c/workspace/ant/build/lib/ant-commons-logging.jar:/usr/local/g > ump/public/workspace/ant/build/lib/ant-jai.jar:/usr/local/gump > /public/workspace/ant/build/lib/ant-jmf.jar:/usr/local/gump/pu > blic/workspace/ant/build/lib/ant-launcher.jar:/usr/local/gump/ > public/workspace/ant/build/lib/ant-jdepend.jar:/usr/local/gump > /public/workspace/ant/build/lib/ant-apache-bsf.jar:/usr/local/ > gump/public/workspace/ant/build/lib/ant-xalan2.jar:/usr/local/ > gump/public/workspace/ant/build/lib/ant-apache-oro.jar:/usr/lo > cal/gump/public/workspace/ant/build/lib/ant-apache-bcel.jar:/u sr/local/gump/public/workspace/ant/build/lib/ant-> trax.jar:/usr/local/gump/public/workspace/ant/build/lib/ant-an tlr.jar:/usr/local/gump/public/workspace/ant/build> /lib/ant-junit.jar:/usr/local/gump/public/workspace/ant/build/ > lib/ant-jsch.jar:/usr/local/gump/public/workspace/ant/build/li > b/ant-javamail.jar:/usr/local/gump/public/workspace/ant/build/ > lib/ant.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant- > stylebook.jar:/usr/local/gump/public/workspace/ant/dist/lib/an > t-jmf.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-sw ing.jar:/usr/local/gump/public/workspace/ant/dist/> lib/ant-trax.jar:/usr/local/gump/public/workspace/ant/dist/lib > /ant-junit.jar:/usr/local/gump/public/workspace/ant/dist/lib/a > nt-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ > ant-xalan2.jar:/us! > r/local/ > gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/g > ump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/publ > ic/workspace/ant/bootstrap/lib/ant-launcher.jar:/usr/local/gum > p/public/workspace/ant/bootstrap/lib/ant.jar:/usr/local/gump/p > ublic/workspace/xml-stylebook/bin/stylebook-1.0-b3_xalan-2.jar :/usr/local/gump/public/workspace/dist/junit/junit> .jar:/usr/local/gump/packages/antlr-2.7.3/antlr.jar:/usr/local > /gump/public/workspace/jakarta-commons/logging/dist/commons-lo gging.jar:/usr/local/gump/public/workspace/jakarta> -commons/logging/dist/commons-logging-api.jar:/usr/local/gump/ > public/workspace/jakarta-commons/net/dist/commons-net-20040527 .jar:/usr/local/gump/packages/jaf-> 1.0.1/activation.jar:/usr/local/gump/public/workspace/jakarta- > bcel/bin/bcel.jar:/usr/local/gump/public/workspace/jakarta-bsf /build/lib/bsf.jar:/usr/local/gump/public/workspac> e/logging-log4j/log4j-20040527.jar:/usr/local/gump/public/work > space/logging-log4j/log4j-chainsaw-20040527.jar:/usr/local/gum > p/public/w
