| 2c7471d3ae15cfaf934467d7d144567f54d6cec0 |
|
15-Nov-2016 |
Prathmesh Prabhu <pprabhu@chromium.org> |
Revert "[autotest] Standardize label logic"
This reverts commit fda3e23ce60251c17bdc213d72b0b575251ea6d1.
Speculatively reverting to un-break push-to-prod
BUG=chromium:665538
TEST=push-to-prod test passes (maybe?). This is a speculative revert.
Change-Id: Ia435c3e220ce0bd3fceabf786b685355bc0488d1
Reviewed-on: https://chromium-review.googlesource.com/411388
Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
/external/autotest/scheduler/prejob_task.py
|
| fda3e23ce60251c17bdc213d72b0b575251ea6d1 |
|
17-Oct-2016 |
Allen Li <ayatane@chromium.org> |
[autotest] Standardize label logic
BUG=None
TEST=Run dummy suite with provisioning locally and run unittest
Change-Id: Ie71009972ea950e1d8402bbbb12e0172c43baffa
Reviewed-on: https://chromium-review.googlesource.com/400618
Commit-Ready: Allen Li <ayatane@chromium.org>
Tested-by: Allen Li <ayatane@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@google.com>
/external/autotest/scheduler/prejob_task.py
|
| 02d7e74c7670ad8dc63b6ea08667522adb229f5a |
|
15-Oct-2016 |
Allen Li <ayatane@chromium.org> |
[autotest] Add milestone to special_task metrics v2
BUG=chromium:650481,chromium:657664
TEST=Run suite in local autotest
Change-Id: I32a064c43725930e7cca9bca864eae8172d45f66
Reviewed-on: https://chromium-review.googlesource.com/400940
Commit-Ready: Allen Li <ayatane@chromium.org>
Tested-by: Allen Li <ayatane@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/scheduler/prejob_task.py
|
| 13bed22affe28b8dab83f953a0825086bcb7b0dc |
|
20-Oct-2016 |
Dan Shi <dshi@google.com> |
Revert "[autotest] Add milestone to special_task metrics"
This reverts commit bcd51502ef7d00bdc2e0c0b0ea42c2c5434ae7c3.
Change-Id: I9f83d6c42141ba2a6942f3afd751870e7bc31e08
Reviewed-on: https://chromium-review.googlesource.com/401020
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Tested-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/scheduler/prejob_task.py
|
| bcd51502ef7d00bdc2e0c0b0ea42c2c5434ae7c3 |
|
15-Oct-2016 |
Allen Li <ayatane@chromium.org> |
[autotest] Add milestone to special_task metrics
BUG=chromium:650481
TEST=Run suite in local autotest
Change-Id: Ie4bfe0f15479830ea0b5b7689f730ae5af6e98c1
Reviewed-on: https://chromium-review.googlesource.com/399580
Commit-Ready: Allen Li <ayatane@chromium.org>
Tested-by: Allen Li <ayatane@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/scheduler/prejob_task.py
|
| ffed172ee1d49f70b996814b481e7af19aae403b |
|
19-May-2016 |
Richard Barnette <jrbarnette@chromium.org> |
[autotest] Report DUT repair status to monarch.
At the end of each special task, if the task knows whether the
target DUT was working or broken, post that information using
ts_mon.
BUG=None
TEST=run repair and verify jobs in a local instance
Change-Id: I713a8584eb66820d890e3733c8790b421720672a
Reviewed-on: https://chromium-review.googlesource.com/345972
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
/external/autotest/scheduler/prejob_task.py
|
| e111759e369647e675337ef89812ddb3f1957666 |
|
19-May-2016 |
Richard Barnette <jrbarnette@chromium.org> |
[autotest] Delete a dead method from class PreJobTask
The _copy_to_results_repository() method was unused, so delete it.
BUG=None
TEST=git grep for the method name
Change-Id: I499794f2f774f68903583cfd5b76f67c132de75c
Reviewed-on: https://chromium-review.googlesource.com/345971
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Paul Hobbs <phobbs@google.com>
/external/autotest/scheduler/prejob_task.py
|
| 7279a5a4048858c23e0e2f651da0beb2283cd2b7 |
|
07-Apr-2016 |
Dan Shi <dshi@google.com> |
[autotest] Sort special tasks based on a predefined priority list.
This is to force ChromeOS provision occurs before firmware provision.
BUG=chromium:517551
TEST=local run a suite with firmware build.
Change-Id: I1147e8d0de154087e37dce8572405a810448e7a6
Reviewed-on: https://chromium-review.googlesource.com/337598
Commit-Ready: Dan Shi <dshi@google.com>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
/external/autotest/scheduler/prejob_task.py
|
| 8e6affb2614b6b6f03ab97b52740f03df1470ade |
|
16-Dec-2015 |
Simran Basi <sbasi@google.com> |
[autotest] Pass in --lab to autoserv for Special Tasks.
Special tasks kick off autoserv in a number of different locations,
this change informs special tasks ran by the scheduler that they
are running in the lab.
BUG=chromium:570125
TEST=Local MobLab run.
Change-Id: I741f64a54bf5ce0997be34435ad7db1a2051e39d
Reviewed-on: https://chromium-review.googlesource.com/318753
Commit-Ready: Simran Basi <sbasi@chromium.org>
Tested-by: Simran Basi <sbasi@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
/external/autotest/scheduler/prejob_task.py
|
| a1f0d02e55fb497e0051c4fee7edc0b99ff378b7 |
|
24-Oct-2014 |
Dan Shi <dshi@chromium.org> |
[autotest] limit repair failed count to the same host and hqe
The limit is added so we won't repeatedly repair a host for a job created
from AFE. The code path has a bug that will set the host in repair failed
status even for jobs created with meta_host, and the host was repair the
first time.
This CL limits the count of repair job to the ones with same host and hqe.
Thus, a host can be tried to be repaired if an hqe failed in multiple hosts.
DEPLOY=scheduler
BUG=chromium:392496,chromium:426905
TEST=local
set max_repair_limit in global config to 0, raise an exception in reset to
force reset to fail.
test frontend job:
Create a job from AFE with a given host. Confirm that the dut goes into repair
failed status and no repair job queued.
test suite job:
create a suite job
When max_repair_limit is set to 0, confirm the duts goes into repair failed
status and no repair job queued.
Wehn max_repair_limit is set to 2, confirm that repair job was created after
reset failure.
Change-Id: Icf737f7ff90a96edd6f08b5d79f431b66313d242
Reviewed-on: https://chromium-review.googlesource.com/225442
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Dan Shi <dshi@chromium.org>
Tested-by: Dan Shi <dshi@chromium.org>
/external/autotest/scheduler/prejob_task.py
|
| df15ec56a94b6f7bad47d1c9d75a57c7b6f7feec |
|
01-Mar-2014 |
Alex Miller <milleral@chromium.org> |
[autotest] Remove label dependant special task actions migration code
BUG=chromium:334418
DEPLOY=sync everywhere, then restart scheduler
TEST=special tasks run fine
Change-Id: Ib0c09095ff323ff53defef33509e1642560da0c6
Reviewed-on: https://chromium-review.googlesource.com/188456
Reviewed-by: Alex Miller <milleral@chromium.org>
Tested-by: Alex Miller <milleral@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
/external/autotest/scheduler/prejob_task.py
|
| ec21225c11b0983b563c24bb71828f5bb6bbcaee |
|
01-Mar-2014 |
Alex Miller <milleral@chromium.org> |
[autotest] Feed job labels from the scheduler to autoserv.
All job labels now get passed into reset, verify, cleanup, provision,
and repair. Everything bug provision can run standalone, and thus
passing the job labels needs to be optional for those.
BUG=chromium:334418
DEPLOY=scheduler
TEST=special tasks run fine, scheduler shows autoserv being invoked
correctly
Change-Id: I524cc8441e654685e50c935fb1d55cf87e8a2f73
Reviewed-on: https://chromium-review.googlesource.com/188455
Reviewed-by: Alex Miller <milleral@chromium.org>
Tested-by: Alex Miller <milleral@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
/external/autotest/scheduler/prejob_task.py
|
| ec1c4b22229677d8654159a6f40bbb9d80199278 |
|
18-Nov-2013 |
beeps <beeps@chromium.org> |
[autotest] Don't mark a host as ready if it failed provision.
Currently we mark a host as ready at the end of provisioning, if
we don't call the hqes on pending. This has the following shortcomings:
1. Even though a repair is queued up against the DUT it won't be
effective till the end of the next tick in handle_agents. This
means the the DUT will join the available hosts pool for the duration
of one tick, and probably get reassigned to an hqe (might even be to
the same hqe). This is undesirable, because we know that the DUT will
switch to having a Repairing status at the end of the same tick.
2. If we have repaired a DUT too many times after a provision, we
would like to switch that DUT to repair failed, this won't happen.
This cl leaves the DUT in provisioning till the next job changes its
state, if the provisioning attempt failed, unless it was a provision
attempt without an hqe.
TEST=Ran suites where provisioning failed.
BUG=chromium:318461
Change-Id: I208287f8e59a241b8e4f6257bca8b2fba23346d2
Reviewed-on: https://chromium-review.googlesource.com/177159
Reviewed-by: Prashanth B <beeps@chromium.org>
Tested-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Prashanth B <beeps@chromium.org>
/external/autotest/scheduler/prejob_task.py
|
| 5e2bb4aa28611aaacaa8798fd07943ede1df46c6 |
|
28-Oct-2013 |
beeps <beeps@chromium.org> |
[autotest] Scheduler refactor.
Break scheduler into simpler modules.
This change also modifies run_pylint to check for undefined variables.
BUG=chromium:312338
TEST=Ran smoke suite against multiple duts.
Triggered agents like repair, verify etc. Pylint, Unittests.
DEPLOY=scheduler
Change-Id: Ibd685a27b5b50abd26cdf2976ac4189c3e9acc0a
Reviewed-on: https://chromium-review.googlesource.com/174080
Commit-Queue: Prashanth B <beeps@chromium.org>
Tested-by: Prashanth B <beeps@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
/external/autotest/scheduler/prejob_task.py
|