Menu
▾
▴
pyret-devel — A list for developer discussion
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(4) |
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
(5) |
Nov
|
Dec
|
|
From: Eduardo V. <edu...@gm...> - 2006-10-13 16:09:26
|
Hello guys,
I would ask you to send master and hunter configuration files and
searchspace
and jobs files which are known as working. In this way I can compare
with my files.
BTW, in doc/searchspace.example there is an entry for search
module configuration:
# Search = MultiHunterRS {
# }
Is it "Search = MultiHunterRS" or "RegressionSearch =
MultiHunterRS" ? I'm asking
this because the Python class is named RegressionSearch, as you can
see at the modules/search directory.
BR,
---
Eduardo Valentin
On 10/11/06, Jason Ruesch <jr...@ja...> wrote:
> Eduardo,
>
> Sorry to hear you're having so many problems. We definitely didn't
> make the project easy to setup!
>
> I believe there still may be another log file that we started using
> and never got rid of completely in the /var/log folder that may
> include the errors you are having.
>
> --Jason Ruesch
>
> On Oct 11, 2006, at 6:35 AM, Eduardo Valentin wrote:
>
> > Hello,
> >
> >
> >
> >
> > Alright, after some permission problems I could do something
> > useful. But I have some
> > questions and some unsolved problems. So, I think that I'm missing
> > something into my
> > configuration files. I used the same master.conf and hunter.conf files
> > I already sent.
> > What's more, I'm executing the PyretMaster.py and PyretHunter.py as
> > root user. Therefore,
> > I'm able to execute the following job file:
> >
> > Copy = LinuxKernelCopy {
> > From = /nfsdrives/var_bubs/repository/cgrepo/linux2/
> > To = /usr/src/linux2/
> > Regex=(.)*
> > CleanUp=False
> > }
> >
> > Build = LinuxKernelBuild {
> > Input = /usr/src/linux2/
> > Arch = i386
> > }
> >
> > Install = LinuxKernelInstall {
> > }
> >
> >
> > Test = LinuxKernelTest {
> > LTPFolderPath = /home/ebv/diversos/ols/pyret/ltp-full-20060717/
> > Scenario = syscalls
> > Duration = 0s
> > }
> >
> >
> > But, I needed to change the install module for Linux Kernels as
> > follows:
> >
> > modules/install/LinuxKernelInstall.py:
> > kernel = "kernel /vmlinuz-PyReT root="+kernel[start+5:];
> >
> > to
> >
> > kernel = "kernel /boot/vmlinuz-PyReT root="+kernel[start+5:];
> >
> > Also, there is a little mistake in the search space example file
> > (docs/searchspace.example):
> >
> > It is:
> > # Test = LinuxKernelTest {
> > # LTPFolderPath = /usr/local/ltp-full-20060105/
> > # TestName = syscalls
> > # TimeOut = 0s
> > # }
> >
> > and should be:
> > # Test = LinuxKernelTest {
> > # LTPFolderPath = /usr/local/ltp-full-20060105/
> > # Scenario = syscalls
> > # Duration = 0s
> > # }
> >
> > However, what I really couldn't setup is the error messaging
> > system. My log files do not
> > print the error messages. There is no useful info there. If something
> > goes wrong, I get something like:
> > Job @time="2006101012107": found job - /nfsdrives/var_bubs/jobs/
> > job03.strongbad
> > Status @time="2006101012107": Hunter is changing status to copying
> > Status @time="2006101012107": Hunter is changing status to patching
> > Status @time="2006101012107": Hunter is changing status to building
> > Status @time="2006101012107": Hunter is changing status to installing
> > Status @time="2006101012107": Hunter is changing status to testing
> > Status @time="2006101012107": Hunter is changing status to idle
> >
> >
> > It just says that is changing from state to state until reach the
> > idle state, whereas the error messages are not displayed (if one
> > parameter is not present/configured for example).
> >
> > Furthermore, I couldn't accomplish a patching phase.
> > Actually, I still couldn't even understand how the automation
> > process works. Specifically,
> > how the patch control is done. I passed a range in my search space:
> >
> > Search = BinaryRS {
> > }
> > MasterPatchSource = LinuxKernelMasterPatchSource {
> > ChangesetStart = e3071039a1389fa767113ef4472040df507f3b02
> > ChangesetEnd = 51775f2daed1fd12472b48335286b7d251ac8cea
> > Dest = /nfsdrives/var_bubs/repository/cgrepo/linux2/
> > PatchDest = /nfsdrives/var_bubs/repository/patches/linux2/
> > }
> >
> > I thought that as I specified a patch range (ChangesetStart and
> > ChangesetEnd variables),
> > it would do the search automatically. But I need to specify a patch ID
> > in my job file:
> > HunterPatchSource = LinuxKernelHunterPatchSource {
> > PatchDest = /nfsdrives/var_bubs/repository/patches/linux2/
> > PatchID = 0a05d26784046b1fde1f4c2aef040c7864478410
> > HunterDest = /usr/src/linux2/
> > }
> >
> > So, how does the automation process work? What wrong am I doing ?
> > Why my hunters does not log error messages?
> >
> > Thanks in advance,
> >
> > BR,
> > ---
> > Eduardo Valentin
> >
> > On 10/10/06, Eduardo Valentin <edu...@gm...> wrote:
> >> Hello Parse,
> >>
> >>
> >> I forgot to mention/explain that the file created was
> >> job01.strongbad.error inside the
> >> "jobs" directory. It contains exatly the same contents of my
> >> initial job file.
> >> Copy = LinuxKernelCopy {
> >> From = /nfsdrives/var_bubs/repository/cgrepo/linux2/
> >> To = /usr/src/linux2/
> >> Regex=(.)*
> >> CleanUp=False
> >> }
> >>
> >> HunterPatchSource = LinuxKernelHunterPatchSource {
> >> PatchDest = /nfsdrives/var_bubs/repository/patches/linux2/
> >> PatchID = 0a05d26784046b1fde1f4c2aef040c7864478410
> >> HunterDest = /usr/src/linux2/
> >> }
> >>
> >> and here is my log for my hunter process:
> >> Status @time="20061091642": Hunter is changing status to copying
> >> Status @time="20061091642": Hunter is changing status to patching
> >> Status @time="20061091642": Hunter is changing status to building
> >> Jog Info @time="2006109161521": Build completed sucessfully
> >> Status @time="2006109161521": Hunter is changing status to installing
> >> Status @time="2006109161521": Hunter is changing status to testing
> >> Status @time="2006109161521": Hunter is changing status to cleanup
> >> Status @time="2006109161521": Hunter is changing status to idle
> >> Job @time="2006101010832": found job - /nfsdrives/var_bubs/jobs/
> >> job03.strongbad
> >> Status @time="2006101010832": Hunter is changing status to copying
> >> Info @time="2006101010930": Copy succesfull
> >> Job Info @time="2006101010930": Copy completed sucessfully
> >> Status @time="2006101010930": Hunter is changing status to patching
> >> Info @time="2006101010930": Applying patch using COMMAND:patch -p1 -i
> >> /nfsdrives/var_bubs/repository/patches/
> >> linux2/0a05d26784046b1fde1f4c2aef040c7864478410Status
> >> @time="2006101010930": Hunter is changing status to idle
> >>
> >>
> >>
> >> Any ideas?
> >>
> >>
> >> Thanks in advance
> >>
> >> BR,
> >>
> >> ---
> >> Eduardo Valentin
> >>
> >>
> >> On 10/10/06, Parse Exception <par...@gm...> wrote:
> >>> Eduardo,
> >>>
> >>> what was in job.error?
> >>>
> >>>
> >>>
> >>> --------------------------------------------------------------------
> >>> -----
> >>> Take Surveys. Earn Cash. Influence the Future of IT
> >>> Join SourceForge.net's Techsay panel and you'll get the chance to
> >>> share your
> >>> opinions on IT & business topics through brief surveys -- and
> >>> earn cash
> >>> http://www.techsay.com/default.php?
> >>> page=join.php&p=sourceforge&CID=DEVDEV
> >>>
> >>> _______________________________________________
> >>> Pyret-devel mailing list
> >>> Pyr...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/pyret-devel
> >>>
> >>>
> >>>
> >>
> >>
> >> --
> >> Eduardo Bezerra Valentin
> >>
> >
> >
> > --
> > Eduardo Bezerra Valentin
> >
> > ----------------------------------------------------------------------
> > ---
> > Using Tomcat but need to do more? Need to support web services,
> > security?
> > Get stuff done quickly with pre-integrated technology to make your
> > job easier
> > Download IBM WebSphere Application Server v.1.0.1 based on Apache
> > Geronimo
> > http://sel.as-us.falkag.net/sel?
> > cmd=lnk&kid=120709&bid=263057&dat=121642
> > _______________________________________________
> > Pyret-devel mailing list
> > Pyr...@li...
> > https://lists.sourceforge.net/lists/listinfo/pyret-devel
>
>
>
--
Eduardo Bezerra Valentin
|
|
From: Eduardo V. <edu...@gm...> - 2006-10-11 12:35:03
|
Hello,
Alright, after some permission problems I could do something
useful. But I have some
questions and some unsolved problems. So, I think that I'm missing
something into my
configuration files. I used the same master.conf and hunter.conf files
I already sent.
What's more, I'm executing the PyretMaster.py and PyretHunter.py as
root user. Therefore,
I'm able to execute the following job file:
Copy = LinuxKernelCopy {
From = /nfsdrives/var_bubs/repository/cgrepo/linux2/
To = /usr/src/linux2/
Regex=(.)*
CleanUp=False
}
Build = LinuxKernelBuild {
Input = /usr/src/linux2/
Arch = i386
}
Install = LinuxKernelInstall {
}
Test = LinuxKernelTest {
LTPFolderPath = /home/ebv/diversos/ols/pyret/ltp-full-20060717/
Scenario = syscalls
Duration = 0s
}
But, I needed to change the install module for Linux Kernels as follows:
modules/install/LinuxKernelInstall.py:
kernel = "kernel /vmlinuz-PyReT root="+kernel[start+5:];
to
kernel = "kernel /boot/vmlinuz-PyReT root="+kernel[start+5:];
Also, there is a little mistake in the search space example file
(docs/searchspace.example):
It is:
# Test = LinuxKernelTest {
# LTPFolderPath = /usr/local/ltp-full-20060105/
# TestName = syscalls
# TimeOut = 0s
# }
and should be:
# Test = LinuxKernelTest {
# LTPFolderPath = /usr/local/ltp-full-20060105/
# Scenario = syscalls
# Duration = 0s
# }
However, what I really couldn't setup is the error messaging
system. My log files do not
print the error messages. There is no useful info there. If something
goes wrong, I get something like:
Job @time="2006101012107": found job - /nfsdrives/var_bubs/jobs/job03.strongbad
Status @time="2006101012107": Hunter is changing status to copying
Status @time="2006101012107": Hunter is changing status to patching
Status @time="2006101012107": Hunter is changing status to building
Status @time="2006101012107": Hunter is changing status to installing
Status @time="2006101012107": Hunter is changing status to testing
Status @time="2006101012107": Hunter is changing status to idle
It just says that is changing from state to state until reach the
idle state, whereas the error messages are not displayed (if one
parameter is not present/configured for example).
Furthermore, I couldn't accomplish a patching phase.
Actually, I still couldn't even understand how the automation
process works. Specifically,
how the patch control is done. I passed a range in my search space:
Search = BinaryRS {
}
MasterPatchSource = LinuxKernelMasterPatchSource {
ChangesetStart = e3071039a1389fa767113ef4472040df507f3b02
ChangesetEnd = 51775f2daed1fd12472b48335286b7d251ac8cea
Dest = /nfsdrives/var_bubs/repository/cgrepo/linux2/
PatchDest = /nfsdrives/var_bubs/repository/patches/linux2/
}
I thought that as I specified a patch range (ChangesetStart and
ChangesetEnd variables),
it would do the search automatically. But I need to specify a patch ID
in my job file:
HunterPatchSource = LinuxKernelHunterPatchSource {
PatchDest = /nfsdrives/var_bubs/repository/patches/linux2/
PatchID = 0a05d26784046b1fde1f4c2aef040c7864478410
HunterDest = /usr/src/linux2/
}
So, how does the automation process work? What wrong am I doing ?
Why my hunters does not log error messages?
Thanks in advance,
BR,
---
Eduardo Valentin
On 10/10/06, Eduardo Valentin <edu...@gm...> wrote:
> Hello Parse,
>
>
> I forgot to mention/explain that the file created was
> job01.strongbad.error inside the
> "jobs" directory. It contains exatly the same contents of my initial job file.
> Copy = LinuxKernelCopy {
> From = /nfsdrives/var_bubs/repository/cgrepo/linux2/
> To = /usr/src/linux2/
> Regex=(.)*
> CleanUp=False
> }
>
> HunterPatchSource = LinuxKernelHunterPatchSource {
> PatchDest = /nfsdrives/var_bubs/repository/patches/linux2/
> PatchID = 0a05d26784046b1fde1f4c2aef040c7864478410
> HunterDest = /usr/src/linux2/
> }
>
> and here is my log for my hunter process:
> Status @time="20061091642": Hunter is changing status to copying
> Status @time="20061091642": Hunter is changing status to patching
> Status @time="20061091642": Hunter is changing status to building
> Jog Info @time="2006109161521": Build completed sucessfully
> Status @time="2006109161521": Hunter is changing status to installing
> Status @time="2006109161521": Hunter is changing status to testing
> Status @time="2006109161521": Hunter is changing status to cleanup
> Status @time="2006109161521": Hunter is changing status to idle
> Job @time="2006101010832": found job - /nfsdrives/var_bubs/jobs/job03.strongbad
> Status @time="2006101010832": Hunter is changing status to copying
> Info @time="2006101010930": Copy succesfull
> Job Info @time="2006101010930": Copy completed sucessfully
> Status @time="2006101010930": Hunter is changing status to patching
> Info @time="2006101010930": Applying patch using COMMAND:patch -p1 -i
> /nfsdrives/var_bubs/repository/patches/linux2/0a05d26784046b1fde1f4c2aef040c7864478410Status
> @time="2006101010930": Hunter is changing status to idle
>
>
>
> Any ideas?
>
>
> Thanks in advance
>
> BR,
>
> ---
> Eduardo Valentin
>
>
> On 10/10/06, Parse Exception <par...@gm...> wrote:
> > Eduardo,
> >
> > what was in job.error?
> >
> >
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share your
> > opinions on IT & business topics through brief surveys -- and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> >
> > _______________________________________________
> > Pyret-devel mailing list
> > Pyr...@li...
> > https://lists.sourceforge.net/lists/listinfo/pyret-devel
> >
> >
> >
>
>
> --
> Eduardo Bezerra Valentin
>
--
Eduardo Bezerra Valentin
|
|
From: Eduardo V. <edu...@gm...> - 2006-10-10 14:21:30
|
Hello Parse,
I forgot to mention/explain that the file created was
job01.strongbad.error inside the
"jobs" directory. It contains exatly the same contents of my initial job file.
Copy = LinuxKernelCopy {
From = /nfsdrives/var_bubs/repository/cgrepo/linux2/
To = /usr/src/linux2/
Regex=(.)*
CleanUp=False
}
HunterPatchSource = LinuxKernelHunterPatchSource {
PatchDest = /nfsdrives/var_bubs/repository/patches/linux2/
PatchID = 0a05d26784046b1fde1f4c2aef040c7864478410
HunterDest = /usr/src/linux2/
}
and here is my log for my hunter process:
Status @time="20061091642": Hunter is changing status to copying
Status @time="20061091642": Hunter is changing status to patching
Status @time="20061091642": Hunter is changing status to building
Jog Info @time="2006109161521": Build completed sucessfully
Status @time="2006109161521": Hunter is changing status to installing
Status @time="2006109161521": Hunter is changing status to testing
Status @time="2006109161521": Hunter is changing status to cleanup
Status @time="2006109161521": Hunter is changing status to idle
Job @time="2006101010832": found job - /nfsdrives/var_bubs/jobs/job03.strongbad
Status @time="2006101010832": Hunter is changing status to copying
Info @time="2006101010930": Copy succesfull
Job Info @time="2006101010930": Copy completed sucessfully
Status @time="2006101010930": Hunter is changing status to patching
Info @time="2006101010930": Applying patch using COMMAND:patch -p1 -i
/nfsdrives/var_bubs/repository/patches/linux2/0a05d26784046b1fde1f4c2aef040c7864478410Status
@time="2006101010930": Hunter is changing status to idle
Any ideas?
Thanks in advance
BR,
---
Eduardo Valentin
On 10/10/06, Parse Exception <par...@gm...> wrote:
> Eduardo,
>
> what was in job.error?
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> _______________________________________________
> Pyret-devel mailing list
> Pyr...@li...
> https://lists.sourceforge.net/lists/listinfo/pyret-devel
>
>
>
--
Eduardo Bezerra Valentin
|
|
From: Parse E. <par...@gm...> - 2006-10-10 13:22:43
|
Eduardo, what was in job.error? |
|
From: Eduardo V. <edu...@gm...> - 2006-10-09 19:34:04
|
hello all,
Sorry for this delay.
I'm trying to reproduce the Linux Kernel Regression Hunting and
I'm facing a problem with the patching and building phases. First, I'm
using only one machine. Here are my files:
master.conf:
###Paths PyReT needs to know about###
sfs=/nfsdrives/var_bubs/
jobs=/nfsdrives/var_bubs/jobs/
jobsDead=/nfsdrives/var_bubs/jobs/dead/
jobsError=/nfsdrives/var_bubs/jobs/error/
jobsFinished=/nfsdrives/var_bubs/jobs/finished/
hunters=/nfsdrives/var_bubs/hunters/
hunterLogs=/nfsdrives/var_bubs/logs/hunters
masterLogs=/nfsdrives/var_bubs/logs/master/
tests=/nfsdrives/var_bubs/tests/
modules=/nfsdrives/var_bubs/modules/
searches=/nfsdrives/var_bubs/searches/
repository=/nfsdrives/var_bubs/repository/
###Modules###
FileSystem=modules.system.LinuxFS
#
# 'ConfigurationFile' is now depricated in the 'master.conf' file
#
#ConfigurationFile=modules.system.LinuxCF
masterLog=modules.system.ASCIILog {
fileName = master.log
}
###Intervals###
jobInterval=2
searchInterval=4
retryLimit=3
###Hunter Interval###
deadTime=5
###Logging####
loggingLevel=5
### max hunters to assign for a search space ###
maxHunters=50000
hunter.conf
###Computer Info###
name=strongbad
###Shared File System###
base=/nfsdrives/var_bubs/
hunters=hunters/
hunterLogs=logs/hunters/
jobs=jobs/
ExecutablePath=/home/ebv/diversos/ols/pyret/PyretHunter.py
###Modules###
FileSystem=LinuxFS
TextFile=TextFile
FileAccess=FileAccess
ConfigurationFile=LinuxCF
System=DebianSystem
HunterLog=ASCIILog
LogFileName=hunter.log
###Logging####
loggingLevel=5
searchspace
Search = BinaryRS {
}
MasterPatchSource = LinuxKernelMasterPatchSource {
ChangesetStart = e3071039a1389fa767113ef4472040df507f3b02
ChangesetEnd = 51775f2daed1fd12472b48335286b7d251ac8cea
Dest = /nfsdrives/var_bubs/repository/cgrepo/linux2/
PatchDest = /nfsdrives/var_bubs/repository/patches/linux2/
}
job01
Search = BinaryRS {
}
MasterPatchSource = LinuxKernelMasterPatchSource {
ChangesetStart = e3071039a1389fa767113ef4472040df507f3b02
ChangesetEnd = 51775f2daed1fd12472b48335286b7d251ac8cea
Dest = /nfsdrives/var_bubs/repository/cgrepo/linux2/
PatchDest = /nfsdrives/var_bubs/repository/patches/linux2/
}
ebv@neumann:~/diversos/ols/pyret$ cat job01
Copy = LinuxKernelCopy {
From = /nfsdrives/var_bubs/repository/cgrepo/linux2/
To = /usr/src/linux2/
Regex=(.)*
CleanUp=False
}
HunterPatchSource = LinuxKernelHunterPatchSource {
PatchDest = /nfsdrives/var_bubs/repository/patches/linux2/
PatchID = 0a05d26784046b1fde1f4c2aef040c7864478410
HunterDest = /usr/src/linux2/
}
Build = LinuxKernelBuild {
Input = /usr/src/linux2/
Arch = i386
}
and here is my nfsdrives tree:
ebv@neumann:/nfsdrives$ tree
.
`-- var_bubs
|-- hunters
| `-- strongbad.idle
|-- jobs
| |-- dead
| |-- error
| |-- finished
|-- logs
| |-- hunters
| | `-- strongbad.log
| `-- master
| |-- master.log
| `-- searchspace.log
|-- modules
|-- repository
| |-- cgrepo
| `-- patches
| `-- linux2
| |-- 0a05d26784046b1fde1f4c2aef040c7864478410
| |-- 51775f2daed1fd12472b48335286b7d251ac8cea
| |-- 829702a4980b5c13dc14f4556c513bc62e4aaec1
| |-- 9c3d91f81f7b467c468971136a231d8160f1ebb6
| `-- f16bdc72dc139e4413e75ef5b91690e9ad8e1b05
|-- searches
| `-- searchspace.proc
`-- tests
So, when I copy the searchspace file to the "searches" directory,
it seams to work.
However, when I copy the job01 file to the "jobs" directory, it does
not do the build phase.
And if copy a job file like:
Copy = LinuxKernelCopy {
From = /nfsdrives/var_bubs/repository/cgrepo/linux2/
To = /usr/src/linux2/
Regex=(.)*
CleanUp=False
}
HunterPatchSource = LinuxKernelHunterPatchSource {
PatchDest = /nfsdrives/var_bubs/repository/patches/linux2/
PatchID = 0a05d26784046b1fde1f4c2aef040c7864478410
HunterDest = /usr/src/linux2/
}
it patched the tree even though the hunter ends with an error
(creates a job.error file)
So, what should I do to accomplish the build phase?
BR,
---
Eduardo Valentin
On 8/8/06, Parse Exception <par...@gm...> wrote:
>
> Sorry only sent this to Jeremy
> ---------- Forwarded message ----------
> From: Parse Exception <par...@gm... >
> Date: Aug 8, 2006 8:55 AM
> Subject: Re: [Pyret-devel] [HOW TO] Examples
> To: Jeremy Wilde <toa...@gm...>
>
>
>
> Does anyone have the bandwidth to whip one up pretty quick?
> maybe Eduardo could help, perhaps with a list of questions,
> maybe we could build a FAQ out of it? Thoughts?
>
> -James
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>
> _______________________________________________
> Pyret-devel mailing list
> Pyr...@li...
> https://lists.sourceforge.net/lists/listinfo/pyret-devel
>
>
>
--
Eduardo Bezerra Valentin
|
|
From: Parse E. <par...@gm...> - 2006-08-08 13:56:35
|
Sorry only sent this to Jeremy ---------- Forwarded message ---------- From: Parse Exception <par...@gm...> Date: Aug 8, 2006 8:55 AM Subject: Re: [Pyret-devel] [HOW TO] Examples To: Jeremy Wilde <toa...@gm...> Does anyone have the bandwidth to whip one up pretty quick? maybe Eduardo could help, perhaps with a list of questions, maybe we could build a FAQ out of it? Thoughts? -James |
|
From: Jeremy W. <toa...@gm...> - 2006-08-07 20:02:27
|
Currently the closest thing we have to that is the README file. Jeremy |
|
From: Eduardo V. <edu...@gm...> - 2006-08-03 11:28:46
|
Hello all, I have just started to play with pyret. I read also the paper present in OLS 2006. This is really an interesting tool. However, I tried to run some tests, but I still a little confused with how things work. Is there any "how to" or examples on how to use PyReT over linux kernel git trees? Thanks in advance, -- Eduardo Bezerra Valentin |
|
From: <jw...@ut...> - 2006-03-01 02:35:41
|
The team here at Neumont is looking to implement a set of modules to allow us to run regression hunts on the SQLite source. At this point the most challenging part looks to be determining changesets in CVS. I have started looking at information on how to get the revision history for the files in the project. I'm wondering if anyone can point me to a resource, and ideally some code that simplifies the task. Right now it looks like its going to be a painstaking process of parsing the output of the CVS commands. It also seems likely that is a duplication of efforts, since other applications access and display this information already. Jeremy Wilde |
|
From: <jw...@ut...> - 2006-01-30 17:19:47
|
The tool for building configuration files is still something we are looking to do, just not something we are starting on right now. Jason rebuilt the machines again late last week and we have started running tests on them again, and so far they are once again behaving well. Jeremy |
|
From: Parse E. <par...@gm...> - 2006-01-30 15:05:25
|
you had mentioned at the onsite a tool to help build the configuration file, as setup can be fairly complex, is this still happening? also how did the set up of the test systems pan out? are you back up and running on the base master/hunter architecture? thanks -Parse On 1/27/06, Jeremy Wilde <Jer...@st...> wrote: > > An update of what current plans for improvement are. > > > > 1. Documentation, comments being added to configuration files, > pydocs being generated, and a document to describe installation and usag. > > 2. Enhancing existing binary search to deal with error conditions > rather than aborting > > 3. New search similar to a binary one that makes use of multiple > hunters. > > 4. A shortcut of the hunter portion of the execution to make testin= g > the master and search spaces quicker and easy to manipulate to test more > code paths. > > 5. Working on being accepted to present at the Ottawa Linux > Symposium > > > > These are in addition to some general code enchancements like a clearner > module organization and bug fixing. > > > > Jeremy > > > > > |
|
From: Jeremy W. <Jer...@st...> - 2006-01-27 22:10:27
|
An update of what current plans for improvement are. =20 1. Documentation, comments being added to configuration files, pydocs being generated, and a document to describe installation and usag. 2. Enhancing existing binary search to deal with error conditions rather than aborting 3. New search similar to a binary one that makes use of multiple hunters. 4. A shortcut of the hunter portion of the execution to make testing the master and search spaces quicker and easy to manipulate to test more code paths. 5. Working on being accepted to present at the Ottawa Linux Symposium =20 These are in addition to some general code enchancements like a clearner module organization and bug fixing. =20 Jeremy =20 =20 |
|
From: Parse E. <par...@gm...> - 2005-12-01 13:19:51
|
As you begin to get closer to a completed proof of concept it might be useful to begin to do releases, that is to say create a tar ball of the cvs tree and put it in files section for download, typically the release will be more stable than the bleeding edge code in the cvs tree, and should have had some basic testing done on it to ensure it builds/runs/works :) -Parse |
|
From: Paul L. <pl...@us...> - 2005-11-16 23:14:50
|
My name is Paul Larson and I work with James on the LTC Test team. I've looked at the design document a little today and have a few questions/comments about it. First, as Nigel already pointed out, NFS being called out specifically seemed a little odd. Was this just an example or is there a particular reason why it needs to be NFS? Is there a mechanism for specifying hardware requirements for the test to run correctly? I talked to James about this and I get the impression now that part of defining the job includes limiting the job to run on a set of specified machines. What would be very nice to see here in the design, is how a job is defined. I would assume that you have some definition of what a job control file should look like? Probably short of a full blown language, but it's worth designing this now and specifying how it should work so that you can poke holes in it and find shortcomings at design time. How is the searchspace definition structured? What is the LoadModules step and what happens at this step? What logging is performed during the build/install/test process? I would think it necessary to log test and log patch status for instance... lets stop here a second. Let's say you have a set of changes in your searchspace A,B,C,D,E,F,G. You know that A-1 passed, and G+1 failed. So you take D, and either pull the changeset, date, or apply the patch. Now lets say it doesn't even build. How do you treat that failure? Probably you want to either back off some, or move forward some because you probably pulled at a point that either had merge patches following it, or a point which broke the build. You cannot say with certainty whether this would have passed the test or failed it though, so this needs an additional state to classify it as both unknown and unusable. It may also be necessary to log some other form of remote output. In terms of kernel testing, this often takes the form of either output over a serial line, or from another ip:port which is redirecting serial output from the box. This comes with additional baggage of needing to have tests specifications that not only includes 0 or non-zero, but also expecting output over this other line. For instance, if your test crashes the machine, then there's probably something in the debug output, or at least loss of heartbeat to the machine that can tell you it failed. Perhaps this goes beyond the scope of what you are trying to accomplish. If so, then it should be explicitly called out in the design that the tool is only being designed with the idea of hunting for non-fatal errors. It is certainly more complicated to allow the searching of fatal errors, but significantly more useful as well. Thanks, Paul Larson |
|
From: Parse E. <par...@gm...> - 2005-11-14 17:24:14
|
First, thanks Nigel for taking a look at the design. I was wondering when I might expect to see code showing up in the cvs tree as well as some indication of who ones which portions of the code and some sort of schedule(Basically I am looking for what should be done this semester). I thought the design looked pretty good, I would like to see a specific document about the details of the kernel reg hunting. I am working to get some more reviewers on board, and then will ask the kernel janitors and OSDL to review the design, you should not however be waiting on them to code. If some solid issues are raised and the design needs to be changed, we can handle that when it occurs. Also we had talked about a white paper for this work, I think your design doc, and the implementation doc for kernel hunts should serve as a solid basis for the paper -Parse |
|
From: Nigel H. <nh...@us...> - 2005-11-10 21:45:19
|
Greetings, I work with James Kenefick on Linux kernel testing. I read the PyReT=20 design document (2nd draft, 11/4/05); and if I understanding it correctly, = you?re designing an infrastructure in which you can build a regression=20 hunting engine. Your document is *not* meant to describe a specific=20 regression hunting algorithm ... right? Here are some initial comments=20 based on this assumption. It appears to be a blackboard-like (work allocation) approach where the=20 Master analyzes the Search Space and creates Jobs to run tests. Hunters=20 idle until they find new jobs. Jobs have the general structure: Load=20 modules, Transport files, Build, ... . Hunters run jobs and create results = files for the Master to process.=20 Automating kernel testing is a great pursuit and your basic mechanism=20 seems okay. I think this is a good start. In general your paper needs a=20 much better introductory description of the problem and overview of the=20 solution. You jump into the solution model too soon. The definitions in=20 the glossary should be incorporated into a design overview that precedes=20 the diagrams. Also, a simple working example would help the reader=20 understand how to use the services provided by your mechanism.=20 The most important thing missing from the document is a clear description=20 of how the ?search space? is used to drive the whole process. Also, the=20 analysis loop is not explicitly shown. I see blocks for ?Process Search=20 Space?, ?Create Jobs?, but ?Evaluate Results? appears to be outside that=20 loop and terminates without feedback into the system. In the Hunter Flow Diagrams (note you have a typo in the diagram name),=20 there are some blocks with multiple out-going archs that are unlabeled.=20 For example, Build, Patch, Install, all have an arch to ?Update Hunter=20 Status? as well as an arch to the next stage. Are both of these archs=20 taken sequentially, or is ?Update Hunter Status? an error path? Nit picks:=20 The reference to an implementation specific protocol, NFS, seems out of=20 place given the otherwise high-level description of your diagrams. The use of Python (also implementation specific) in the project name could = lead some to presume you?re testing Python. nigel. |
|
From: Paul F. <pa...@gm...> - 2005-11-03 22:05:47
|
If you get this message, you are subscribed to the Pyret-Devel Mailing list= . If you receive this message by error, please remove yourself via the Pyret project at www.sourceforge.net <http://www.sourceforge.net>. Please disregard this message, it is only a test. Thank You, ~ Gnom3 |
|
From: Paul F. <pa...@gm...> - 2005-10-28 19:47:25
|
The source-forge homepage for pyret has been updated with a brief project description. We will expand this as the project grows and more information is required. The first draft of pyret's design will be submitted on Monday for review by our friends at IBM. We will be taking a look at any feedback we receive while working on the final design that should be completed by Thursday, November 3rd. The initial draft of the design will consist of a system flow diagram, technical specs for the Master, Hunter, and the Module API. Specs for the initial module implementation (for performing hunts in Linux Kernels) will be completed as soon as the API is complete. ~ Paul Fox |
|
From: Parse E. <par...@gm...> - 2005-10-27 01:27:14
|
Well I found the list today. but was wondering when I am going to see a project description on the web page |
1 message has been excluded from this view by a project administrator.
