Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@5360 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@5359 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
unittests.
Signed-off-by: Mihai Rusu <dizzy@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@4565 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
the lists to compare them
Signed-off-by: Jean-Marc Eurin <jmeurin@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@4334 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
when scraping rsync output.
Signed-off-by: Scott Zawalski <scottz@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@4295 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
Fix permissions for all the development tree
Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@4094 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
access the dictionary entries returned by the RPC call so it breaks when
using dictionary syntax on those. Fixed and updated unittests.
Signed-off-by: Mihai Rusu <dizzy@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@3964 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
have it ask the control file generation RPC generate server side code to
download and send to the client the kernel config file and make it aware
of the new location. This allows to have clients receive kernel config
files that they cannot access otherwise. It requires that the tests
given to map_action are server side tests.
Signed-off-by: Mihai Rusu <dizzy@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@3963 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
instead of doing its own generation logic. Updated sample config file
and unittests.
Signed-off-by: Mihai Rusu <dizzy@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@3910 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
when connecting to the frontend (which will be set as the owner for the
job).
Signed-off-by: Mihai Rusu <dizzy@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@3782 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
git-svn-id: svn://test.kernel.org/autotest/trunk@3621 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
- create a set when filtering the kernel files so that duplicates are
removed
- update the known kernels db before running the triggers not after
because triggers are allowed to run for a long time and if one runs
mirror while another mirror is already running the second one will again
find the same new kernel files that the first one found
Signed-off-by: Mihai Rusu <dizzy@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@3598 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
employing a fcntl.flock() based process synchronization to protect
against 2 or more processes updating the db at the same time. Also
switched to using a temporary file to protect against write failures
(like disk full) situations from corrupting the existent data. Updated
unittest.
Signed-off-by: Mihai Rusu <dizzy@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@3596 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
written in Python code syntax to allow for much greater configuration
flexibility. Also introduced the concept of a persistent database to
store the list of known kernels (written an implementation that uses
cPickle), the concept of a "source" object that provides the current
list of kernels (written implementations for rsync and urllib2/HTML
sources). Exposed the actions configured with the trigger object to the
config file so anyone can configure whatever actions they want taken to
handle the new kernel versions. Provided sample config file.
When setting up the mirror script on a new installation you will
probably want (after creating a config file for it) to run it first in
"dry run" mode to initialize the database with the known kernels
reported by the source at that moment (otherwise it will think all those
kernels are new and will want to run whatever actions you configured on
all of them).
Signed-off-by: Mihai Rusu <dizzy@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@3477 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
confuse some tools that attempt to detect what the file is. Best to just
not have them there.
Signed-off-by: Jesse Keating <jkeating@redhat.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@3407 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
- removed builtin support for kernel patches as this is already
handled by kernelextract tool (and it wasn't used by mirror anyways)
- removed "queuedir" command line argument and updated it to use
server.frontend API for creating the jobs on the server
- grouped jobs by control-file/kernel-config tuple to avoid scheduling a
job per machine when not necessary
Signed-off-by: Mihai Rusu <dizzy@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@2931 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
Signed-off-by: Martin J. Bligh <mbligh@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@2909 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
git-svn-id: svn://test.kernel.org/autotest/trunk@1933 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
Signed-off-by: Travis Miller <raphtee@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@1824 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@1658 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
scripts
Risk: Medium/High
Summary: After going trough the autotest tree, removing all places where
we have statements like
#!/usr/bin/python2.4
As they're unnecessary for those who have python > 2.4. Still, we want
to make sure we're running on something > 2.4 for those scripts, so I
hooked the scripts to the common lib infrastructure when needed. I tried
to be as careful as possible to make sure all scripts worked after my
modifications, I could even spot an import problem on
server/standalone_profiler.py and fix it.
Also, while I was there, I fixed several inconsistencies on the
mirror/mirror script.
Signed-off-by: Lucas Meneghel Rodrigues <lucasmr@br.ibm.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@1527 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
Signed-off-by: Martin J. Bligh <mbligh@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@719 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
From: Ryan Stutsman <stutsman@google.com>
Ok, final rework to this mirror script. From here bugs should be easy
to fix as patches.
This version should address all the concerns you outlined in your
prior looks at the mirror script.
The major addition of this version is automatic smart kernel config
selection for builds.
It works like this: you pass a directory to mirror via the -f flag
like so:
mirror -f /home/testing/config -c /home/testing/client_test_mapping
/home/testing/mirror /home/testing/queue
Now, when a new kernel release is found it will test that kernel on
each machine listed in the client_test_mapping file with each of the
control files listed on that line.
For example, if client_test_mapping contains:
machine1 ~/basic-tests ~/do-something.srv
machine2 ~/basic-tests
It will queue the AutoTest control file ~/basic-tests on both machines
and the ~/do-something.srv Autoserv file just on machine1. The
Autoserv file support should make it quite easy to do similar testing
with RPMs, for example, though the mirroring urls and regexps would
probably have to modified or configurable.
In doing this for AutoTest control files it will wrap it with the code
necessary to build and boot the kernel version it mirrored. If there
is a file in /home/testing/config with the name machine1, for example,
it will use that to determine which kernel build config should used.
If there where a /home/testing/config/machine1 like this:
2.6.0 /boot/config-2.6.18
2.6.19 /boot/config-2.6.21
Then for any kernel 2.6.0 or later it will build it with
/boot/config-2.6.18 (path on the *client* machine). For any kernel
2.6.19 or later it will use /boot/config-2.6.21.
If no file exists for that machine it will simply use /boot/config.
Also, if the kernel version to be tested it older than any config in
the mapping it will automatically use the oldest in the file (2.6.0 ==
/boot/config-2.6.18) in this case.
The /home/testing/mirror arg tells it to mirror the kernel.org
releases to that directory and /home/testing/queue contains the queues
that correspond to the names given in client_test_mapping.
Hopefully this all makes sense. I'll be watching the list to see if
there are questions or bugs to work out with the script. I have
tested it somewhat and it seems to work as expected.
git-svn-id: svn://test.kernel.org/autotest/trunk@692 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
git-svn-id: svn://test.kernel.org/autotest/trunk@373 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
git-svn-id: svn://test.kernel.org/autotest/trunk@344 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
Signed-off-by: Martin J. Bligh <mbligh@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@306 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
Signed-off-by: Martin J. Bligh <mbligh@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@303 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
git-svn-id: svn://test.kernel.org/autotest/trunk@302 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
file
git-svn-id: svn://test.kernel.org/autotest/trunk@301 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
Signed-off-by: Martin J. Bligh <mbligh@google.com>
git-svn-id: svn://test.kernel.org/autotest/trunk@300 592f7852-d20e-0410-864c-8624ca9c26a4
|
|
git-svn-id: svn://test.kernel.org/autotest/trunk@299 592f7852-d20e-0410-864c-8624ca9c26a4
|