| 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/scheduler_config.py
|
| b92af21b84c5e27af7f2023ea54409c124d0968e |
|
10-Apr-2015 |
Paul Hobbs <phobbs@google.com> |
[autotest] Remove per-tick process restriction.
The per-tick process restriction was causing a performance problem
when a tick took a long time, and there isn't a good reason to keep
the per-tick process constraint as there is already a total process
constraint.
TEST=Ran the scheduler. The unit tests pass.
BUG=chromium:471352
Change-Id: I2b669fb758fbcc898e1727da51bd6d4cd99cd5d2
Reviewed-on: https://chromium-review.googlesource.com/265072
Trybot-Ready: Paul Hobbs <phobbs@google.com>
Tested-by: Paul Hobbs <phobbs@google.com>
Commit-Queue: Paul Hobbs <phobbs@google.com>
Reviewed-by: Fang Deng <fdeng@chromium.org>
/external/autotest/scheduler/scheduler_config.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/scheduler_config.py
|
| 1a18905776c0a53e2a169f61dbf5bdad3bd0cb74 |
|
28-Oct-2013 |
Dan Shi <dshi@chromium.org> |
[autotest] revert suite throttling
Undo CL:
https://chromium-review.googlesource.com/#/c/167175
keep stats call and _notify_process_limit_hit.
BUG=chromium:
TEST=suite runn in local setup, unittest
DEPLOY=scheduler
Change-Id: I713b69651fabfb8cbb4f9c1ca3a8605900753bc9
Reviewed-on: https://chromium-review.googlesource.com/174896
Commit-Queue: Dan Shi <dshi@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
/external/autotest/scheduler/scheduler_config.py
|
| 9a0c6c39b649877077cb50fe60ec991fb5b5d42e |
|
05-Sep-2013 |
Fang Deng <fdeng@chromium.org> |
[autotest] Send an email if a drone is hitting process limit
Add a setting 'max_processes_warning_threshold' to global_config.ini.
If the raitio of active processes to max processes goes over
the threshold, DroneManager will send a email to
chromeos-lab-infrastructure@.
To prevent it from spamming our mailing list, only one email
will be sent for each drone within 24 hours.
BUG=chromium:277184
TEST=Test locally and confirm email is sent out when
the threshold is reached.
DEPLOY=scheduler
Change-Id: Id4a883ff6c26e9bba384974c255a0ce0f3cb4056
Reviewed-on: https://chromium-review.googlesource.com/168147
Reviewed-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
Tested-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Fang Deng <fdeng@chromium.org>
/external/autotest/scheduler/scheduler_config.py
|
| a4a78efbc0ab93bb57ddc1ea010a30b5c07a7ace |
|
04-Sep-2013 |
Alex Miller <milleral@chromium.org> |
[autotest] Add retries to provisioning.
There is now a setting in global_config.ini which controls provision
retries, and this value can be reloaded on-the-fly in the scheduler.
Be cautioned that provision failures are basically silently hid.
There's currently no sort of reporting to indicate that a retry
happened.
Implementing this also pointed out the way to clean up the ProvisionTask
code, so there's also some free cleanup packaged into this CL.
BUG=chromium:279667
DEPLOY=scheduler
TEST=forced provision failures, and watched the HQE get requeued a
finite number of times.
Change-Id: I66d967fb8f3ab9f199571764821e1a39d0e81f39
Reviewed-on: https://chromium-review.googlesource.com/167990
Reviewed-by: Dan Shi <dshi@chromium.org>
Tested-by: Alex Miller <milleral@chromium.org>
Reviewed-by: Prashanth Balasubramanian <beeps@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
/external/autotest/scheduler/scheduler_config.py
|
| c23a7f0357a6109c7e3ed91798d0d433f5de0a21 |
|
28-Aug-2013 |
Alex Miller <milleral@chromium.org> |
[autotest] Throttle HostlessQueueEntries.
This is a quick hack to throttling the number of suites we have active.
I'd like if there was a nice easy way to single out what a suite is, or
have a job elect to be throttled, but in terms of making sure the system
doesn't go down again soon for the same reason, this will be good enough
for now.
Note that, while throttled, the suite jobs show as running, but the
autoserv process isn't kicked off.
BUG=chromium:279627
DEPLOY=scheduler
TEST=Kicked off multiple suites with max_hostless_processes set to 500.
All ran. Set max_hostless_processes to 1, and reloaded via :13467.
Scheduled another suite, which didn't start running until all other
suites finished.
Change-Id: I141a9bc4bd64d9a40c1ec4cd05a624739bb85076
Reviewed-on: https://chromium-review.googlesource.com/167175
Tested-by: Alex Miller <milleral@chromium.org>
Reviewed-by: Fang Deng <fdeng@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
/external/autotest/scheduler/scheduler_config.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/scheduler_config.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/scheduler_config.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/scheduler_config.py
|
| 77182562edaaeeffcb98f48a7236a727136aa8ec |
|
10-Jun-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Have the scheduler wait a configurable amount of time before starting
atomic group jobs as soon as minimum synch count hosts are available
in Pending state up until AtomicGroup.max_number_of_hosts are available.
Adds a DelayedCallTask class to monitor_db along with logic in the Job
class to use this to delay the job becoming ready to run for a little
while as well as making sure the job is run at the end of the delay
without needing to wait for another host to change state.
Signed-off-by: Gregory Smith <gps@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@3236 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/scheduler_config.py
|
| 324bf819a4ea0fb2fa2509c3b4462f208e225d8d |
|
21-Jan-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
Make maximum process throttling configurable on a per-drone basis.
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2660 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/scheduler_config.py
|
| d1ee1dd3f3e5ac44f00d7a96deb815dbe1beedad |
|
07-Jan-2009 |
showard <showard@592f7852-d20e-0410-864c-8624ca9c26a4> |
* move some scheduler config options into a separate module, scheduler_config
* add a little embedded HTTP server to the scheduler, defined in status_server.py, running in a separate thread. this displays loaded config values and allows reloading of those config values at runtime. in the future we can extend this to do much more.
* make global_config handles empty values as nonexistent values by default. otherwise, we would have to both pass a default= and check for value == '' separately. Now, we just pass default= and it's all taken care of.
Signed-off-by: Steve Howard <showard@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2608 592f7852-d20e-0410-864c-8624ca9c26a4
/external/autotest/scheduler/scheduler_config.py
|