hello:
i am studying sesat, i want all sources of it and detailed development
documents!how can I get it? Thank you!
[EMAIL PROTECTED] 写道：
Send Kernel-development mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://sesat.no/mailman/listinfo/kernel-development
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Kernel-development digest..."
Today's Topics:
1. Error while executing forked tests. (Andreas Ringdal)
2. Re: Error while executing forked tests. (Mick Semb Wever)
3. Re: Error while executing forked tests. (Andreas Ringdal)
4. Re: Error while executing forked tests. (Mick Semb Wever)
5. Re: Error while executing forked tests. (Andreas Ringdal)
----------------------------------------------------------------------
Message: 1
Date: Mon, 14 Apr 2008 12:56:12 +0200
From: "Andreas Ringdal" <[EMAIL PROTECTED]>
Subject: [Kernel-development] Error while executing forked tests.
To: [email protected]
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
System: Windows Server 2003
Created a new image and installed all requirements stated on sesat.no
-----------
System variables
C:\source\sesat-kernel\trunk>set
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\Administrator\Application Data
CATALINA_BASE=C:\Program Files\Apache Software Foundation\Tomcat 6.0
CATALINA_HOME=C:\Program Files\Apache Software Foundation\Tomcat 6.0
CLIENTNAME=IF-ANDREAS
ClusterLog=C:\WINDOWS\Cluster\cluster.log
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=SESAT
ComSpec=C:\WINDOWS\system32\cmd.exe
ERROR_CODE=1
FP_NO_HOST_CHECK=NO
HOME=C:\Documents and Settings\Administrator
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\Administrator
JAVA_HOME=C:\program files\java\jdk1.6.0_05
LOGONSERVER=\\SESAT
NUMBER_OF_PROCESSORS=4
OS=Windows_NT
Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\apache-maven\bin;C:\program
files\java\jdk1.6.0_05\bin
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 4 Stepping 8, GenuineIntel
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=0408
ProgramFiles=C:\Program Files
PROMPT=$P$G
SESSIONNAME=RDP-Tcp#1
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\8
TMP=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\8
USERDOMAIN=IF-SESAT
USERNAME=Administrator
USERPROFILE=C:\Documents and Settings\Administrator
windir=C:\WINDOWS
Screndump
[...]
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running TestSuite
[org.testng.internal.annotations.JDK14AnnotationFinder] [WARNING] Invalid
source directory C:\source\sesat-kernel\trunk\generic.sesam\wa
r\src\test\java ignored
[Parser] Running:
C:\source\sesat-kernel\trunk\generic.sesam\war\src\test\resources\testng.xml
killed.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error while executing forked tests.; nested exception is
org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.Comm
andLineException: Error while executing external command, process killed.
Process timeout out after 600 seconds
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error while
executing forked tests.; nested exception is org.apache.maven.surefi
re.booter.shade.org.codehaus.plexus.util.cli.CommandLineException: Error
while executing external command, process killed.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error while
executing forked tests.; nested exception is org.apache.maven.sur
efire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException: Error
while executing external command, process killed.
at
org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:485)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
... 16 more
Caused by: org.apache.maven.surefire.booter.SurefireBooterForkException:
Error while executing forked tests.; nested exception is org.ap
ache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException:
Error while executing external command, process kill
ed.
at
org.apache.maven.surefire.booter.SurefireBooter.fork(SurefireBooter.java:666)
at
org.apache.maven.surefire.booter.SurefireBooter.forkSuites(SurefireBooter.java:468)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesForkOnce(SurefireBooter.java:368)
at
org.apache.maven.surefire.booter.SurefireBooter.run(SurefireBooter.java:241)
at
org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:481)
... 18 more
Caused by:
org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineException:
Error while executing external comm
and, process killed.
at
org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java
:195)
at
org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java
:95)
at
org.apache.maven.surefire.booter.SurefireBooter.fork(SurefireBooter.java:662)
... 22 more
Caused by: java.lang.InterruptedException: Process timeout out after 600
seconds
at
org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java
:156)
... 24 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 11 minutes 52 seconds
[INFO] Finished at: Mon Apr 14 12:20:27 CEST 2008
[INFO] Final Memory: 32M/59M
[INFO]
------------------------------------------------------------------------
C:\source\sesat-kernel\trunk>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://sesat.no/pipermail/kernel-development/attachments/20080414/75c22e9c/attachment-0001.htm
------------------------------
Message: 2
Date: Mon, 14 Apr 2008 13:04:27 +0200
From: Mick Semb Wever <[EMAIL PROTECTED]>
Subject: Re: [Kernel-development] Error while executing forked tests.
To: "Sesat Kernel usage and development discussions."
<[email protected]>
Cc: Andreas Ringdal <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
On Mon, 2008-04-14 at 12:56 +0200, Andreas Ringdal wrote:
> System: Windows Server 2003
> Created a new image and installed all requirements stated on sesat.no
I'd suggest running w/ -DskipTests=true
(if that fails -Dmaven.test.skip=true)
Tests work on linux, but w/ mac and windows we are still having some
troubles. Of course all the information you can provide w/ tests failing
is welcome, especially on windows machines (currently we don't have any
developers on windows machines).
~mck
--
"The possibility that we may fail in the struggle should not deter us
from supporting a cause we believe to be just." Abraham Lincoln
| semb.wever.org | sesat.no | sesam.no |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url :
http://sesat.no/pipermail/kernel-development/attachments/20080414/67f60e66/attachment-0001.pgp
------------------------------
Message: 3
Date: Mon, 14 Apr 2008 13:13:09 +0200
From: "Andreas Ringdal" <[EMAIL PROTECTED]>
Subject: Re: [Kernel-development] Error while executing forked tests.
To: "Mick Semb Wever" <[EMAIL PROTECTED]>
Cc: "Sesat Kernel usage and development discussions."
<[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1
If you can provide me with some quick steps on how tohget the
information you need, that can be arranged.
Andreas
On 4/14/08, Mick Semb Wever <[EMAIL PROTECTED]> wrote:
> On Mon, 2008-04-14 at 12:56 +0200, Andreas Ringdal wrote:
> > System: Windows Server 2003
> > Created a new image and installed all requirements stated on sesat.no
>
> I'd suggest running w/ -DskipTests=true
> (if that fails -Dmaven.test.skip=true)
>
> Tests work on linux, but w/ mac and windows we are still having some
> troubles. Of course all the information you can provide w/ tests failing
> is welcome, especially on windows machines (currently we don't have any
> developers on windows machines).
>
> ~mck
>
> --
> "The possibility that we may fail in the struggle should not deter us
> from supporting a cause we believe to be just." Abraham Lincoln
> | semb.wever.org | sesat.no | sesam.no |
>
------------------------------
Message: 4
Date: Mon, 14 Apr 2008 13:20:50 +0200
From: Mick Semb Wever <[EMAIL PROTECTED]>
Subject: Re: [Kernel-development] Error while executing forked tests.
To: Andreas Ringdal <[EMAIL PROTECTED]>
Cc: "Sesat Kernel usage and development discussions."
<[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
> If you can provide me with some quick steps on how tohget the
> information you need, that can be arranged.
All i can see so far is that the tests timeout. Infact this timeout is a
setting in the pom.xml.
Is there anything useful in the test reports found under the
target/surefire-reports/ directories?
~mck
--
"The Matrix is the world that has been pulled over your eyes to blind
you from the truth."
| semb.wever.org | sesat.no | sesam.no |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url :
http://sesat.no/pipermail/kernel-development/attachments/20080414/98d8ee72/attachment-0001.pgp
------------------------------
Message: 5
Date: Mon, 14 Apr 2008 21:25:23 +0200
From: "Andreas Ringdal" <[EMAIL PROTECTED]>
Subject: Re: [Kernel-development] Error while executing forked tests.
To: "Sesat Kernel usage and development discussions."
<[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
C:\source\sesat-kernel\trunk\generic.sesam\war\target\test-logs\test.log
DEBUG 11:37:54,577 (FileResourceLoader.java:getResource)-project
generic.sesam\
DEBUG 11:37:54,577 (FileResourceLoader.java:getResource)-basedirNormalised
file:/C:/source/sesat-kernel/trunk/generic.sesam/war/
DEBUG 11:37:54,577 (FileResourceLoader.java:getResource)-basedirNormalised
file:/C:/source/sesat-kernel/trunk/war/
DEBUG 11:37:54,577 (FileResourceLoader.java:getResource)-basedirNormalised
file:/C:/source/sesat-kernel/war
DEBUG 11:37:54,577 (FileResourceLoader.java:getResource)-basedirNormalised
file:/C:/source/war
DEBUG 11:37:54,577 (FileResourceLoader.java:getResource)-basedirNormalised
file:/C:/war
DEBUG 11:37:54,577 (FileResourceLoader.java:getResource)-basedirNormalised
file:/war
DEBUG 11:37:54,577 (FileResourceLoader.java:getResource)-basedirNormalised
file:/../war
DEBUG 11:37:54,577 (FileResourceLoader.java:getResource)-basedirNormalised
file:/../../war
DEBUG 11:37:54,577 (FileResourceLoader.java:getResource)-basedirNormalised
file:/../../../war
This kept going on and extending the path by another /.. until it had filled
the disk with a 14 GB log file
On Mon, Apr 14, 2008 at 1:20 PM, Mick Semb Wever <[EMAIL PROTECTED]>
wrote:
> > If you can provide me with some quick steps on how tohget the
> > information you need, that can be arranged.
>
> All i can see so far is that the tests timeout. Infact this timeout is a
> setting in the pom.xml.
> Is there anything useful in the test reports found under the
> target/surefire-reports/ directories?
>
> ~mck
>
> --
> "The Matrix is the world that has been pulled over your eyes to blind
> you from the truth."
> | semb.wever.org | sesat.no | sesam.no |
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://sesat.no/pipermail/kernel-development/attachments/20080414/aa958499/attachment.htm
------------------------------
_______________________________________________
Kernel-development mailing list
[email protected]
http://sesat.no/mailman/listinfo/kernel-development
End of Kernel-development Digest, Vol 5, Issue 7
************************************************
_______________________________________________
Kernel-development mailing list
[email protected]
http://sesat.no/mailman/listinfo/kernel-development
