| 3536b98cf0f552eb9c4d8d6dc0403423166da9f5 |
|
29-Aug-2011 |
Mike Truty <truty@chromium.org> |
Fix django 1.3 DeprecationWarning for DATABASES.
Django 1.3 which we migrated to, modified the settings structure so that
the database settings are no longer a set of constants. They are replaced
with a dictionary of dictionaries where the 'default' dictionary contains
the desired settings. I've switched to that format to avoid the warning. Not
sure when those constants will actually stop working.
This is the actual message that no longer shows:
/usr/local/autotest/site-packages/django/db/__init__.py:19: DeprecationWarning:
settings.DATABASE_* is deprecated; use settings.DATABASES instead.
TEST=ran dashboard generation on local autotest
Change-Id: I647f2c353b67a0ec820895c7973bfffab84f3f87
Reviewed-on: http://gerrit.chromium.org/gerrit/6835
Reviewed-by: Lucas Meneghel Rodrigues <lookkas@gmail.com>
Tested-by: Lucas Meneghel Rodrigues <lookkas@gmail.com>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Tested-by: Mike Truty <truty@chromium.org>
/external/autotest/frontend/afe/test.py
|
| a5288b4bb2b09aafe914d0b7d5aab79a7e433eaf |
|
28-Jul-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Upgrade from Django 0.96 to Django 1.0.2.
Risk: high (framework change)
Visibility: medium
Signed-off-by: James Ren <jamesren@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3457 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/frontend/afe/test.py
|
| 2e490cc4d9aaaf7419db0c8bd7271171dcf747fa |
|
08-Oct-2008 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
-refactor frontend/afe/test.py to make it reusable by new_tko
-make frontend_unittest.py use code in django_test_utils instead of its own copy
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2255 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/frontend/afe/test.py
|
| 8493a9fd99aae21ccfdd4cb5cb84bde43ca0c153 |
|
04-Aug-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Fixed the doctest to be consistent with our 4 spaces no tabs change, and fixed test.py to ignore files that end in ~.
Signed-off-by: Travis Miller <raphtee@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1956 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/frontend/afe/test.py
|
| 4205d8965f7fdda6a9c24100be912f36f04a3fc9 |
|
14-Jul-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Fix the unittest to make it pass and avoid relying on a fragile parser:
- Use the __import__ and import coherently
- Use the standard unittest framework
Rewrite of the barrier unittest as using fork() completely messed up
the overall test suite and ran it 8 times.
Visibility: Medium/High - some import changes
Risk: Medium
Tests:
- Ran unittest_suite.py for all and individual directories
- Ran coverage_suite.py for all and individual directories
- Ran manage.py test from frontend directory.
Signed-off-by: Jean-Marc Eurin <jmeurin@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1827 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/frontend/afe/test.py
|
| 2de8f901d7ec910faa3b02e4c6f512563a5d72fe |
|
13-Jun-2008 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
-change frontend_unittest to execute the unittests directly (as opposed to executing them through manage.py in a separate process). this should get us coverage data. the unit tests could still be better integrated into the whole suite, but this is an improvement.
-some fixes to doctests related to tab-space conversion
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1702 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/frontend/afe/test.py
|
| 0afbb6369aa5aa9a75ea67dd9e95ec4b21c0c181 |
|
06-Jun-2008 |
jadmanski <jadmanski@592f7852-d20e-0410-864c-8624ca9c26a4> |
Convert all python code to use four-space indents instead of eight-space tabs.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1658 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/frontend/afe/test.py
|
| 58ff09df13d02ffa71b66a0b60a324bc74c5908e |
|
29-May-2008 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Enforce doctest ordering. This is necessary since the different doctest files depend on each other.
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1565 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/frontend/afe/test.py
|
| f699a2c208726acfbe4e004c419a8dcc06fba04e |
|
10-Apr-2008 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Provide a unittest wrapper around Django's "manage.py test" so the
unittest_suite will include the Django unit tests.
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1422 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/frontend/afe/test.py
|
| 5c7e819b5f770656e4440989b153140823b1977b |
|
08-Apr-2008 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
-don't run pylint as part of the frontend unit test suite
-don't look for doctests in files that start with .
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1415 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/frontend/afe/test.py
|
| e8819cdf80ca0e0602d22551a50f970aa68e108d |
|
15-Feb-2008 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add frontend and scheduler for Autotest
The attached tarball includes the new Autotest web frontend for creating
and monitoring jobs and the new scheduler for executing jobs. We've
been working hard to get these complete and stabilized, and although
they still have a long, long way to go in terms of features, we believe
they are now stable and powerful enough to be useful.
The frontend consists of two parts, the server and the client. The
server is implemented in Python using the Django web framework, and is
contained under frontend/ and frontend/afe. The client is implemented
using Google Web Toolkit and is contained under frontend/client. We
tried to use Dojo initially, as was generally agreed on, but it proved
to be too young and poorly documented of a framework, and developing in
it was just too inefficient.
The scheduler is contained entirely in the scheduler/monitor_db Python
file. It looks at the database used by the web frontend and spawns
autoserv processes to run jobs, monitoring them and recording status.
The scheduler was developed by Paul Turner, who will be sending out some
detailed documentation of it soon.
I've also included the DB migrations code for which I recently submitted
a patch to the mailing list. I've included this code because it is
necessary to create the frontend DB, but it will (hopefully) soon be
part of the SVN repository.
Lastly, there is an apache directory containing configuration files for
running the web server through Apache.
I've put instructions for installing a full Autotest server, including
the web frontend, the scheduler, and the existing "tko" results backend,
at http://test.kernel.org/autotest/AutotestServerInstall. I've also
created a brief guide to using the web frontend, with plenty of
screenshots, at http://test.kernel.org/autotest/WebFrontendHowTo.
Please let me know if you find any problems with either of these pages.
Take a look, try it out, send me comments, complaints, and bugs, and I
hope you find it useful!
Steve Howard, and the rest of the Google Autotest team
From: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@1242 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/frontend/afe/test.py
|