| 0f261debdbba7664ef7b0eacbac0e7daba89eebd |
|
02-Feb-2017 |
Allen Li <ayatane@chromium.org> |
[autotest] [atomic] Remove atomic groups from scheduler
BUG=chromium:681906
TEST=Run unittest suite
Change-Id: If9c144aae8d2a8df567a5a03b02bc3fec5d14c0d
Reviewed-on: https://chromium-review.googlesource.com/435565
Commit-Ready: Allen Li <ayatane@chromium.org>
Tested-by: Allen Li <ayatane@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@google.com>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 5e2efb71ffebead22aa4f0744ad843ee79814b43 |
|
07-Feb-2017 |
Dan Shi <dshi@google.com> |
[autotest] Use the metrics_mock object in case chromite is not set up.
BUG=chromium:688166
TEST=unittest
Change-Id: Ic0077cb2dba75a8d820f229060f3f70f507850a1
Reviewed-on: https://chromium-review.googlesource.com/438754
Commit-Ready: Dan Shi <dshi@google.com>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Dan Shi <dshi@google.com>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| c29b4c7ec10db41f38e0361febe9846a95629b5a |
|
15-Dec-2016 |
Aviv Keshet <akeshet@chromium.org> |
autotest: delete some email alerts; replace some with monarch metrics
For email alerts that seem (based on searching my email) to never be
sent, I simply deleted them.
For those that are sent sometimes and seem easily amenable to a monarch
metric instead, I changed them to a metric.
This is a first step; there are still many remaining unneccesary email
alerts.
BUG=chromium:672726
TEST=None
Change-Id: Ib1d3715e618623faa16f3faaceabf4218dbad49a
Reviewed-on: https://chromium-review.googlesource.com/420468
Commit-Ready: Aviv Keshet <akeshet@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 598671c5efb6cacd564a71e0c92bcc897d10afc1 |
|
23-Nov-2016 |
Shuqian Zhao <shuqianz@chromium.org> |
[autotest] remove autotest_stats from monitor_db_cleanup
BUG=chromium:667171
TEST=unittest
Change-Id: I962df6f564f6608645a4813d04200a682aa1fe00
Reviewed-on: https://chromium-review.googlesource.com/413633
Commit-Ready: Dan Shi <dshi@google.com>
Tested-by: Shuqian Zhao <shuqianz@chromium.org>
Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| f2c9ac9f514b2c56799974c98c896ae03119c34d |
|
17-Sep-2016 |
Aviv Keshet <akeshet@chromium.org> |
autotest: add stats around db cleanup time
Note, this change requires 386284 to be pushed to prod before it can
land.
CQ-DEPEND=CL:386284
BUG=chromium:626423
TEST=None
Change-Id: Ie78b731a2797574c89f3a0f855ed2f80768395a2
Reviewed-on: https://chromium-review.googlesource.com/386333
Commit-Ready: Aviv Keshet <akeshet@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 0a1bb171d722230a19a067d823679d55068f9c2a |
|
18-Sep-2016 |
Dan Shi <dshi@google.com> |
[autotest] Optimize query to abort timed out tests in monitor_db_cleanup
Replace join with subquery to fasten the query.
BUG=chromium:641290
TEST=local run, unittest
Change-Id: Ic4bc55bc6122dfb1d70b9b06c96e3dc4629ba5e8
Reviewed-on: https://chromium-review.googlesource.com/386791
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 3762c6b48420043b48c33b952a918eba44af152d |
|
17-Sep-2016 |
Dan Shi <dshi@google.com> |
[autotest] Optimize query in monitor_db_cleanup
BUG=chromium:641290
TEST=local run
Change-Id: Id46be265d4c4d1bd5ef2b44ea41d6e7b17202de9
Reviewed-on: https://chromium-review.googlesource.com/386361
Commit-Ready: Dan Shi <dshi@google.com>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Zelidrag Hornung <zelidrag@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 55d5899addf09ad0fa4a6ea7260e7c7b143b430b |
|
05-May-2015 |
Dan Shi <dshi@chromium.org> |
[autotest] Queue calls in drone after drone refresh.
Drone refresh is done in a non-thread safe fashion. It starts the refresh at
the beginning of the tick, then follow by couple other operations, then wait
for the refresh to finish. When it starts, it executes all queued calls in
drone using drone_utils. After drone_utils finishes processing the calls,
the scheduler will empty the queued calls in drones.
That means any calls added between the drone refresh is started and the
completion of drone refresh will be removed without being called.
This CL moves the cleanup call after the drone refresh, also add a comment
about potential future issues. A better fix might fix the root cause. For
example, add a tracker in each drone's call queue. After drone refresh is done,
only clear the calls being processed within refresh. crbug.com/484715 is filed
to track this issue.
BUG=chromium:484039
TEST=local scheduler run, make sure lxc_cleanup is kicked off and finished.
Change-Id: I1bb3229a3da578299949a00af25b3d4674eeed4b
Reviewed-on: https://chromium-review.googlesource.com/269255
Trybot-Ready: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 4ecb004eb95b59977354337d4c8d13ba16b182f9 |
|
04-May-2015 |
Dan Shi <dshi@chromium.org> |
[autotest] Disable lxc_cleanup task to avoid scheduler crash.
BUG=chromium:484039
TEST=None
Change-Id: Ia1c03275792b1c1681c6cbc5e8a202c6c3441b69
Reviewed-on: https://chromium-review.googlesource.com/268991
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
Trybot-Ready: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| c458f66959fde1d934abfff92d20b2dbf115b9c2 |
|
29-Apr-2015 |
Dan Shi <dshi@chromium.org> |
[autotest] Add lxc_cleanup to TwentyFourHourUpkeep of the scheduler.
So scheduler can kick off lxc_cleanup script in each drone every 24 hours.
cron job requires puppet change and it's not supported in moblab.
BUG=chromium:479383
TEST=start scheduler locally, check logs/lxc_cleanup.log to confirm the
script finished running.
Change-Id: I83ebfd6b0888b6f3b2c58d1f3824a692660bd4f7
Reviewed-on: https://chromium-review.googlesource.com/268318
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
Trybot-Ready: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| b715ea477b64ac4814fea81f7988ee4ef353e9a0 |
|
24-Feb-2015 |
Fang Deng <fdeng@chromium.org> |
Revert "[autotest] Teach the scheduler to recover stuck hosts"
This reverts commit a6c0d253e16cf6ddf94a75ef56e50e376b09411c.
Change-Id: Id430e6d563345d39f55d2335da3ee5f2918da205
Reviewed-on: https://chromium-review.googlesource.com/253020
Reviewed-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Fang Deng <fdeng@chromium.org>
Tested-by: Fang Deng <fdeng@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| a6c0d253e16cf6ddf94a75ef56e50e376b09411c |
|
12-Feb-2015 |
Fang Deng <fdeng@chromium.org> |
[autotest] Teach the scheduler to recover stuck hosts
If we have hosts stuck in a state without a task or hqe the
scheduler should recover the host.
The correctness of this CL relies on the fact that
- the scheduler is single threaded and
- in the epilog of a task agent, deactivation of the
special task/hqe, if occurs, must always occur together with
updating host status to the right status within the same tick,
otherwise we will have race condition on updating the host status.
BUG=chromium:432549
TEST=add unittest. run scheduler, manually corrupt the database,
and observer the host is recovered.
DEPLOY=scheduler
Change-Id: Iab39fd5301e14cfa9623ae09ab80589dac9c7564
Reviewed-on: https://chromium-review.googlesource.com/249010
Tested-by: Fang Deng <fdeng@chromium.org>
Reviewed-by: Mungyung Ryu <mkryu@google.com>
Commit-Queue: Fang Deng <fdeng@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 1e1c41b1b4a1b97c0b7086b8430856ed45e064d3 |
|
05-Feb-2015 |
Gabe Black <gabeblack@chromium.org> |
graphite: Separate out configuration from the statsd classes.
The new version of the statsd classes should be created using an instance of
the new Statsd class which sets up some defaults without having to specify
them over and over. This makes it essentially compatible with the existing
usage in autotest, but will allow chromite to configure things differently and
avoid having side effects from importing the module or global state.
BUG=chromium:446291
TEST=Ran unit tests, ran stats_es_functionaltest.py, ran the
stats_mock_unittest, ran a butterfly-paladin tryjob with --hwtest, testing by
fdeng.
DEPLOY=apache,scheduler,host-scheduler
Change-Id: I1071813db197c0e5e035b4d8db615030386f1c1c
Reviewed-on: https://chromium-review.googlesource.com/246428
Reviewed-by: Fang Deng <fdeng@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Gabe Black <gabeblack@chromium.org>
Tested-by: Gabe Black <gabeblack@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| ac189f3c6cafa7d445162b5ec54e4162d0e679b2 |
|
23-Jun-2014 |
Alex Miller <milleral@chromium.org> |
[autotest] Remove indirection in scheduler config.
We shouldn't encourage things to be named two different things in two
different places.
BUG=None
DEPLOY=scheduler
TEST=ran scheduler
Change-Id: I0cfac73f7c2dbc0130f0399d96feda257915cd34
Reviewed-on: https://chromium-review.googlesource.com/205720
Reviewed-by: Prashanth B <beeps@chromium.org>
Reviewed-by: Fang Deng <fdeng@chromium.org>
Tested-by: Alex Miller <milleral@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| da8c60af1e1e3ee97170c700d0b72991687e35a2 |
|
03-Jun-2014 |
Michael Liang <michaelliang@chromium.org> |
[autotest] Migrate graphite directory to client/common_lib/cros
This change allows us to report stats in client tests.
1. Change import paths for all files that import modules from graphite
2. Clean up some unused modules
Related CL: https://chromium-review.googlesource.com/#/c/202467/
BUG=chromium:237255
TEST=Ran scheduler locally, scheduled reboot jobs, verified stats such as monitor_db_cleanup.user_cleanup._cleanup were reported on chromeos-stats.
DEPLOY = apache, scheduler, host_scheduler
Change-Id: Iebfe3b8acc1c363a0b70ea555744e85d1367cb67
Reviewed-on: https://chromium-review.googlesource.com/202727
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Michael Liang <michaelliang@chromium.org>
Tested-by: Michael Liang <michaelliang@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 742b81d29617aab913cf512dbeeccd8606049a57 |
|
30-May-2014 |
Simran Basi <sbasi@chromium.org> |
[autotest] move django.sessions cleanup from 24 hours to 5 mins.
Currently on Moblab our database's ibdata1 file is hitting its max
size causing all sorts of database problems. We suspect this is due
to the lack of cleanup of the django.sessions table and are now going
to run this as part of the 5 min cleanup vs the 24 hour cleanup.
BUG=chromium:379199
TEST=Schedule is running on fresh moblab image.
Change-Id: Ibd5261591b5edebd7cafb46a311e2513c1ca713e
Reviewed-on: https://chromium-review.googlesource.com/202317
Reviewed-by: Alex Miller <milleral@chromium.org>
Tested-by: Simran Basi <sbasi@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 4ec9867f46deb969c154bebf2e64729d56c3a1d3 |
|
15-May-2014 |
Prashanth B <beeps@google.com> |
[autotest] Split host acquisition and job scheduling II.
This cl creates a stand-alone service capable of acquiring hosts for
new jobs. The host scheduler will be responsible for assigning a host to
a job and scheduling its first special tasks (to reset and provision the host).
There on after, the special tasks will either change the state of a host or
schedule more tasks against it (eg: repair), till the host is ready to
run the job associated with the Host Queue Entry to which it was
assigned. The job scheduler (monitor_db) will only run jobs, including the
special tasks created by the host scheduler.
Note that the host scheduler won't go live till we flip the
inline_host_acquisition flag in the shadow config, and restart both
services. The host scheduler is dead, long live the host scheduler.
TEST=Ran the schedulers, created suites. Unittests.
BUG=chromium:344613, chromium:366141, chromium:343945, chromium:343937
CQ-DEPEND=CL:199383
DEPLOY=scheduler, host-scheduler
Change-Id: I59a1e0f0d59f369e00750abec627b772e0419e06
Reviewed-on: https://chromium-review.googlesource.com/200029
Reviewed-by: Prashanth B <beeps@chromium.org>
Tested-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 04be2bd5e4666a5c253e9c30ab20555e04286032 |
|
08-May-2014 |
Ilja H. Friedel <ihf@chromium.org> |
Autotest: Change logging.warn() to logging.warning().
logging.warn() is deprecated. See
http://bugs.python.org/issue13235
Substitution was performed via
~/cros/src/third_party/autotest/files$ find ./ -type f | xargs sed -i 's/logging.warn(/logging.warning(/'
BUG=None.
TEST=There should be one-- and preferably only one --obvious way to do it.
Change-Id: Ie5665743121a49f7fbd5d1f47896a7c65e87e489
Reviewed-on: https://chromium-review.googlesource.com/198793
Commit-Queue: Ilja Friedel <ihf@chromium.org>
Tested-by: Ilja Friedel <ihf@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 372613d54bdfd1b708a5d41ced9a80e209e6dc6a |
|
05-May-2014 |
Prashanth B <beeps@google.com> |
[autotest] Sanity check host assignments.
Check that we haven't violated any correctness constraints by
assigning the same host to 2 simultaneously active jobs. These
changes are in preperation for eventually breaking host assignment
out of the scheduler. The performance degradation should be negligable
since we're only querying for the host_ids of currently active jobs,
every 5 minutes.
TEST=Ran suites, unittests.
BUG=None
DEPLOY=Scheduler
Change-Id: Ie560a67861f9e4d1d59cda9828fb9d2ef433e5f4
Reviewed-on: https://chromium-review.googlesource.com/198196
Reviewed-by: Prashanth B <beeps@chromium.org>
Tested-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 7e60574f3baa0b3928623216a74a770f19d2c316 |
|
12-Nov-2013 |
Simran Basi <sbasi@chromium.org> |
Autotest: Update RPC, Scheduler and AFE to use timeout_mins.
Now that timeout_mins is in the database, we need to update the
infrastructure to display and utilize timeout_mins rather than
timeout.
The scheduler now aborts based off of timeout_mins.
The afe displays/creates jobs using timeout_mins rather than timeout.
The RPC's take in timeout and timeout_min depending on what is inputted
to the system. Note the value supplied for timeout_mins takes precedence
over timeout.
BUG=chromium:221264
TEST=Created job through AFE, run_suite with smoke suite, job_unittest
and rpc_unittests.
DEPLOY=apache, afe, scheduler
CQ-DEPEND=I09f8b6023a31dcef37e98c298dc0d63b37bc0a9e
Change-Id: I838cd1ff85a2ce6bd49fe96bf18fd82be608c758
Reviewed-on: https://chromium-review.googlesource.com/176605
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Simran Basi <sbasi@chromium.org>
Tested-by: Simran Basi <sbasi@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| ee632915c6709ae493ae485f3f4d063a7e7497f7 |
|
09-Oct-2013 |
Alex Miller <milleral@chromium.org> |
[autotest] Add timers to scheduler cleanup.
The peaks of scheduler cleanup are also starting to get high enough that
I'd like to take a look at trying to lessen them a bit. I'm guessing
there's some indexing work to be done here, but I don't know which
queries to target.
BUG=chromium:305408
DEPLOY=scheduler
TEST=Ran scheduler
Change-Id: Ibc1924a90c2502b38e6c7e1058f675f497877369
Reviewed-on: https://chromium-review.googlesource.com/172320
Tested-by: Alex Miller <milleral@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 34217022229b755bc1ee52f83665acba76bd5044 |
|
06-Nov-2012 |
Simran Basi <sbasi@chromium.org> |
Autotest: Increase run timeout granularity
This CL modifies all references to max_runtime_hrs to instead be
max_runtime_mins. This includes the django models, rpc interfaces, the
cleanup timeout code, and the frontend java views.
The frontend java code will need to be recompiled once this commits to
prevent the frontend from breaking.
The cleanup timeout pathway has been adjusted to find all timedout jobs
by minute, and has been changed to run every 5 minutes vs every hour as
before.
BUG=chromium-os:36067
TEST=Ran on my local afe, ensure that jobs can still be created correctly,
and jobs with short timeouts do indeed get aborted when expected.
Change-Id: Idfdeb3f1d4947d6b2e6b48127a31db535704e972
Reviewed-on: https://gerrit.chromium.org/gerrit/37827
Tested-by: Simran Basi <sbasi@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Ready: Simran Basi <sbasi@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| a8a0d75c2591ab872f695d7b8f22f2ca10493dab |
|
08-Nov-2012 |
Scott Zawalski <scottz@chromium.org> |
Revert "Autotest: Increase run timeout granularity"
This causes autoupdate problems, see bug crosbug.com/36183
This reverts commit daffa57a6738c2a80caee1f311a527313ece1207
Change-Id: Iad65be9bf1b0ea329866bfdc764b0089c4f9b2a5
Reviewed-on: https://gerrit.chromium.org/gerrit/37657
Commit-Ready: Scott Zawalski <scottz@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Tested-by: Scott Zawalski <scottz@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| daffa57a6738c2a80caee1f311a527313ece1207 |
|
06-Nov-2012 |
Simran Basi <sbasi@chromium.org> |
Autotest: Increase run timeout granularity
This CL modifies all references to max_runtime_hrs to instead be
max_runtime_mins. This includes the django models, rpc interfaces, the
cleanup timeout code, and the frontend java views.
The frontend java code will need to be recompiled once this commits to
prevent the frontend from breaking.
The cleanup timeout pathway has been adjusted to find all timedout jobs
by minute, and has been changed to run every 5 minutes vs every hour as
before.
BUG=chromium-os:36067
TEST=Ran on my local afe, ensure that jobs can still be created correctly,
and jobs with short timeouts do indeed get aborted when expected.
Change-Id: Id7668bbd05a9b02c22e7c549fac232fae02fc728
Reviewed-on: https://gerrit.chromium.org/gerrit/37479
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Ready: Simran Basi <sbasi@chromium.org>
Tested-by: Simran Basi <sbasi@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 1c5b0572f6cbc3b210ef0c5a92c73ed681abe16d |
|
11-Oct-2012 |
Simran Basi <sbasi@chromium.org> |
Autotest: Have the scheduler fix active and complete queue entries.
Currently as part of the scheduler's 24 hour cleanup, it looks for
entries that are marked as both active=True and complete=True and
if it finds any such entries, it sends out an email that will repeat
daily till the database is fixed.
In order to address this and have the code self correct the problem,
the 24 hour cleanup will now mark the entries as not active as they
are completed.
BUG=chromium-os:35220
TEST=Tested on my local scheduler where I manually set active=Complete=1
and ensured the error occured and when the fix was put in, it self
corrected.
Change-Id: I954fb4f93753ae843a0cd3169e96d03d3bc63ba3
Reviewed-on: https://gerrit.chromium.org/gerrit/35292
Commit-Ready: Simran Basi <sbasi@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Tested-by: Simran Basi <sbasi@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 5649cff32e9d9cfb5f686b6b4fa08a81f640b553 |
|
13-Aug-2012 |
Scott Zawalski <scottz@google.com> |
Trunce django_session table instead of cleanning it up.
The table django_session is used to keep track of connections and
reuse sessions that have been created. As it currently stands this is
not really respected/used in the Autotest framework and this table
just ends up growing to ridiculous sizes with no benefit.
Truncating the table offers a quick way of clearing all entries we
have accrued with no side effects. As opposed to cleaning up the table
which adds processing overhead to the database and lag when restarting
the scheduler or when it hits its maintenance window.
TEST=Ran truncate on the test server and during RPC/Web page
accesses to ensure that we do not impact scripts or page loads.
BUG=chromium-os:31608
STATUS=Fixed
Change-Id: I600284ef231f2a6943d35e7a72e4fed1328475d7
Reviewed-on: https://gerrit.chromium.org/gerrit/30013
Commit-Ready: Scott Zawalski <scottz@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Tested-by: Scott Zawalski <scottz@chromium.org>
/external/autotest/scheduler/monitor_db_cleanup.py
|
| e0493a4af57c1a73376a7bafaed542c01f588196 |
|
15-Nov-2010 |
Eric Li <ericli@chromium.org> |
Merge remote branch 'cros/upstream' into tempbranch
BUG=
TEST=
Review URL: http://codereview.chromium.org/4823005
Change-Id: I5d56f1c10d0fce7f9d7dc3ad727ea52dcb9b2d6c
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 675bfe7a50b47c1de15248a3894258b312f2123c |
|
19-Feb-2010 |
jamesren <jamesren@592f7852-d20e-0410-864c-8624ca9c26a4> |
Change email of hosts without platforms to a warning in the logs. We don't do anything about this and it is just extra spam for us at this point in time.
This will only affect admins who use the SCHEDULER.notify_email variable
Signed-off-by: Scott Zawalski <scottz@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4258 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/monitor_db_cleanup.py
|
| be030fbb848ad116769790ee0ed149409652c501 |
|
15-Jan-2010 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
In periodic reverificaiton, use schedule_special_task() instead of straight object creation. This is the right path to use for creating tasks -- it include duplication avoidance and automatic owner tagging.
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4120 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 64a9595406f2884fb3ece241190b10aa054439a9 |
|
13-Jan-2010 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
When using Django models from a script, make the current user default to an actual database user named "autotest_system". This allows for simpler, more consistent code.
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4114 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 8dbd05aa0a62a0b17bf4b19131250a8f6cfccf02 |
|
12-Jan-2010 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Implement periodic reverification of dead hosts, configurable in global_config. Implemented as part of the periodic cleanup, so the frequency of reverification is bounded by the periodic cleanup interval. I felt this would be acceptable and putting this in the existing cleanup class makes things more nicely organized.
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4100 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/monitor_db_cleanup.py
|
| eab66ce582bfe05076ff096c3a044d8f0497bbca |
|
23-Dec-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Rename the tables in the databases, by prefixing the app name. This is
in preparation for merging the two databases and the two Django
projects into one.
Note that this renames *all* standard Autotest DB tables in both the
autotest_web and tko databases. If you have scripts written directly
against these databases, *they will break*. If your scripts access
the RPC interfaces, they should continue to work.
Another patch will be along within the next few weeks to actually move
the TKO tables into the autotest_web database.
From: James Ren <jamesren@google.com>
Signed-off-by: Steve Howard <showard@google.com>
Rename the tables in the databases, by prefixing the app name. This is
in preparation for merging the two databases and the two Django projects
into one.
Note that this renames *all* standard Autotest DB tables in both the autotest_web and tko databases. If you have scripts written directly against these databases, *they will break*. If your scripts access the RPC interfaces, they should continue to work.
From: James Ren <jamesren@google.com>
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@4040 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 7ca9e01f5ef84af6e4f0649d8291e05ee158e833 |
|
10-Nov-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Remove the synch_job_start_timeout_minutes scheduler "feature" as it is
pretty much broken by design as is by being based off of the job create time
rather than the time the job's hosts went into Pending.
Its not being used so its easier to remove it.
Signed-off-by: Gregory Smith <gps@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3921 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/monitor_db_cleanup.py
|
| dabf6cf739c42c5641c89f083ce697617ec82d82 |
|
09-Sep-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
It is okay for hosts to have multiple atomic group labels so long as all
of them are associated with the same atomic group. Don't whine in this
situation.
Signed-off-by: Gregory Smith <gps@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3675 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 1ef218db76c473c28627377d8f50d6e6c6743289 |
|
03-Aug-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
This is the result of a batch reindent.py across our tree.
As Martin pointed out, we ought to be more careful and
create a pre-svn commit script to avoid inserting trash
in the tree, meanwhile, this is a good start to cleanup
things
Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3487 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 6157c63947d2d628d187a084acb0a48473af1c79 |
|
06-Jul-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Make the scheduler robust to finding a HostQueueEntry with more than one
atomic group label. Log a detailed error message and continue rather than
bailing out with a SchedulerError.
Signed-off-by: Gregory Smith <gps@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3373 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 01a5167f13d9788c9f359ebba31358e329c98ebc |
|
29-May-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Have the scheduler check for and sometimes cleanup various DB inconsistencies.
* in periodic cleanup, check for relationships to invalidated objects, and remove them (and send notification email)
* in 24hr cleanup, check for hosts with != 1 platform, and send notification email
Also changed AFE models to have labels remove associations with tests (as dependencies) when deleted (invalidated).
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3185 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 12f3e3212795a539d95973f893ac570e669e3a22 |
|
13-May-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Add job maximum runtime, a new per-job timeout that counts time since the job actually started.
* added started_on field to host_queue_entries, so that we could actually compute this timeout
* added max_runtime_hrs to jobs, with default in global config, and added option to create_job() RPC
* added the usual controls to AFE and the CLI for the new job option
* added new max runtime timeout method to
* added migration to add new fields and set a safe default max runtime for existing jobs
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3132 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/monitor_db_cleanup.py
|
| 915958db04ca97d3d5a011383e736a3e2b4e8db3 |
|
22-Apr-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Fix monitor_db_unittest, broken by previous change to refactor cleanup code. Two main things here:
* 24hr cleanup was running upon object construction, which meant it was running inadvertently during unit testing. Fixed this with the usual trick of moving that action from the constructor to an initialize() function, which gets called separately in monitor_db and which the unit test avoids.
* one of the scheduler unit tests was actually testing cleanup code; change that to call the newly located function. this test should maybe be moved to a separate unit test file for the monitor_db_cleanup module, but I just want to get things working again for now.
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3029 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/monitor_db_cleanup.py
|
| f3294cce1590d9c79cb25dcaa18cec0ac08c9b73 |
|
08-Apr-2009 |
mbligh <mbligh@592f7852-d20e-0410-864c-8624ca9c26a4> |
Move clean up functions into seperate file/classes
Add 24hour clean up run
Add django_session clean up
Signed-off-by: Scott Zawalski <scottz@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2979 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/monitor_db_cleanup.py
|