Testsuite: org.apache.avalon.util.env.EnvTest Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 1.756 sec
Testcase: testEnvVariable took 1.622 sec
Caused an ERROR
Failed to access PAT environment variable - Environment process failed with non-zero
exit code of 1
org.apache.avalon.util.env.EnvAccessException: Failed to access PAT environment
variable - Environment process failed with non-zero exit code of 1
at org.apache.avalon.util.env.Env.getUnixShellVariable(Env.java:464)
at org.apache.avalon.util.env.Env.getEnvVariable(Env.java:119)
at org.apache.avalon.util.env.EnvTest.testEnvVariable(EnvTest.java:61)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:232)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
at org.apache.commons.jelly.tags.core.IfTag.doTag(IfTag.java:88)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
at com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:128)
at com.werken.werkz.Goal.fire(Goal.java:639)
at com.werken.werkz.Goal.attain(Goal.java:575)
at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
at com.werken.werkz.Goal.attain(Goal.java:573)
at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
at com.werken.werkz.Goal.attain(Goal.java:573)
at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:448)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:360)
at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:378)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
at com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:128)
at com.werken.werkz.Goal.fire(Goal.java:639)
at com.werken.werkz.Goal.attain(Goal.java:575)
at com.werken.werkz.Goal.attainPrecursors(Goal.java:488)
at com.werken.werkz.Goal.attain(Goal.java:573)
at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:448)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:348)
at org.apache.maven.cli.App.doMain(App.java:543)
at org.apache.maven.cli.App.main(App.java:1109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
Testcase: testEnvVariableTestcase: testEnv took 0.115 sec
btw, PROMPT is not defined. PATH is.
On Nov 10, 2003, at 9:22 PM, Alex Karasulu wrote:
Ok update the environment directory - basically do a cvs up in avalon/merlin/util/env and rerun the tests. Let me know what happens.
If there is no PROMPT or PATH variables in your shell it will bomb out. These variables are present by the way in almost all UNIX'es I know of and hence my reason for using tests for their presence.
Let me know how it turns out. I'll stay up just for you.
Alex
-----Original Message----- From: Steven Harris [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 12:13 AM To: Avalon Developers List Subject: Re: [Merlin] Failure on linux in meta tree
Failed :'-( sniffle sniffle. Cheers, Steve
On Nov 10, 2003, at 3:20 PM, Alex Karasulu wrote:
Thanks much!
-----Original Message----- From: Steve Harris [mailto:[EMAIL PROTECTED] Sent: Monday, November 10, 2003 5:37 PM To: Avalon Developers List Subject: RE: [Merlin] Failure on linux in meta tree
Love too. I can do it tonight. I don't have a mac here at work. but I'll do it tonight. Cheers, Steve
-----Original Message----- From: Alex Karasulu [mailto:[EMAIL PROTECTED] Sent: Mon 11/10/2003 2:31 PM To: 'Avalon Developers List' Cc: Subject: RE: [Merlin] Failure on linux in meta tree Also I want to double check that the format of the output is the same as the /etc/passwd file. You mind sending me your output in an attachment?
Alex
-----Original Message----- From: Steve Harris [mailto:[EMAIL PROTECTED] Sent: Monday, November 10, 2003 5:03 PM To: Avalon Developers List Subject: RE: [Merlin] Failure on linux in meta tree
I thought I already responded with that info?
"nidump passwd /"
will print out the virtual /etc/passwd file to stdout and from that you can do exactly what you do on all other unix based os's
Is that to much of a hack or something. I can ask around for a better way if it is.
I attached the file for the "hello" failure but don't know what file to send for the failure from the avalon/meta failure.
Cheers, Steve
-----Original Message----- From: Stephen McConnell [mailto:[EMAIL PROTECTED] Sent: Mon 11/10/2003 1:50 PM To: Avalon Developers List Cc: Subject: Re: [Merlin] Failure on linux in meta tree
Steve Harris wrote:
heheh,
Yes, I'm on linux, running maven-1.0-beta-10 and getting those two problems.
It seems the tutorials are building but failing a test.
&*$^%***!
The meta thing seems like the same error I was getting on OS X with the meta directory but I'm not sure and I don't have an OS X box here at work.
Ok - it you take a look at the test report you should have some
specific
details - that will help. In the meantime - any chance you can find
out
the information that Alex needs to close the OS X issue?
Stephen.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
------------------------------------------------------------------- --
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]
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
