| 52ac9370d76ce669435589b71d0fdc57ef85535b |
|
23-Mar-2015 |
Fang Deng <fdeng@chromium.org> |
[autotest] Add logging to suite_scheduler
TEST=unittest
BUG=chromium:468993
Change-Id: Iff68ed3df514283fa78a7ca29ce3793901403811
Reviewed-on: https://chromium-review.googlesource.com/261949
Reviewed-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Fang Deng <fdeng@chromium.org>
Tested-by: Fang Deng <fdeng@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|
| 33ea03b85c3f3b40be2813b4e5a87c8a2f3e9f8d |
|
18-Feb-2015 |
Fang Deng <fdeng@chromium.org> |
[autotest] Suite scheduler looks at the correct window for builds
Suite scheduler runs the following git command to find
candidate builds.
git log build-name/samus-release/pass/ --since='1 days ago'
As more and more boards are added, by the time a board is
evaluated, it might have been a couple of hours away from
the original deadline. And using '1 days ago' which is relative
to current timestamp is not accurate. This CL
makes suite scheduler calculate the window using 'deadline'.
E.g. '1 days ago' would mean the window between
|deadline - 1 day| and |deadline|.
BUG=chromium:458236
TEST=unittest;Run suite scheduler
Change-Id: I7495d6fd2668cf84a9f5159e7b6353325a5b2614
Reviewed-on: https://chromium-review.googlesource.com/250600
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Fang Deng <fdeng@chromium.org>
Tested-by: Fang Deng <fdeng@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|
| c9c2a8620c256fa17d16e6ddfa9a007a63f79fe2 |
|
26-Jun-2013 |
J. Richard Barnette <jrbarnette@chromium.org> |
[autotest] Retry `git clone` failures in suite_scheduler.
In suite_scheduler, `git` failures trigger e-mail notifications.
After these failures, suite_scheduler terminates and restarts,
whereupon its first action is to attempt `git clone`. To prevent
e-mail spam storms, we retry that initial clone at startup for a
time before giving up and sending the mail.
BUG=chromium:244530
TEST=unit tests
DEPLOY=suite_scheduler
Change-Id: I19f94285a634b4044a6ff0fcf93f1b47cbb4b315
Reviewed-on: https://gerrit.chromium.org/gerrit/59995
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
Commit-Queue: Richard Barnette <jrbarnette@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|
| 0d00357df2bb69ac799fa1ac6ca81bb68b137c78 |
|
18-Mar-2013 |
Alex Miller <milleral@chromium.org> |
[autotest] Admit that suite_scheduler can't always parse everything.
Esoteric builds have been causing us problems, first |pgo-release|, now
|depthcharge-firmware|. Rather than trying to intelligently understand
how to parse these names and schedule against them, even though no one
is even trying to run out-of-line suites against them, let's just
acknowledge the builds that we can't parse, log it so that it's obvious
what's going on, and continue on.
BUG=chromium:218079, chromium-os:39283
TEST=unit, forced a lumpy-release run
Change-Id: I49de7029893bcea2047fecb09ea33835a7168aaa
Reviewed-on: https://gerrit.chromium.org/gerrit/45763
Commit-Queue: Alex Miller <milleral@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
Tested-by: Alex Miller <milleral@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|
| c7960d16423e63510f105c007e0e22b5a1d4a01f |
|
18-Mar-2013 |
Alex Miller <milleral@chromium.org> |
[autotest] Teach suite_scheduler how to parse depthcharge builds.
It's pgo-release all over again... I really do need to sit down and
write a better fix to this one day.
BUG=chromium:218079
TEST=unit
Change-Id: I95729a40dc68c547523dcfa1acf7b7ad6e960366
Reviewed-on: https://gerrit.chromium.org/gerrit/45758
Tested-by: Alex Miller <milleral@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|
| da26f4ff84cba8a384b53b21354154f68d0d6032 |
|
07-Mar-2013 |
Alex Miller <milleral@chromium.org> |
[autotest] Schedule tests against lumpy-pgo-release builds correctly.
I now understand how this code should work. For the moment, I'm going
to treat pgo-release as a bare branch. If the build team ever decides
that they want to do pgo-release across multiple versions, there's going
to be some suite_scheduler rework needed to be able to specify
milestones on non-release branches.
With this change, we will not schedule suites on lumpy-pgo-release by
default, but if one does want to start scheduling against pgo-release
builds, one can add a stanza to suite_scheduler.ini with
|branch_specs: pgo-release| in the stanza.
BUG=chromium-os:39283
TEST=unit, forced dummy suite on lumpy-pgo-release
Change-Id: I8042a5788cfa58333402cd2660be989c6ea67800
Reviewed-on: https://gerrit.chromium.org/gerrit/44874
Tested-by: Alex Miller <milleral@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|
| 71384cf5f0c9755b45c24fbf27fdc0c770059fa7 |
|
04-Mar-2013 |
Alex Miller <milleral@chromium.org> |
Revert "[autotest] Schedule tests against lumpy-pgo-release builds."
Although this is the correct way to parse, it causes us to schedule
tests against lumpy-pgo-release, which is not what is wanted. There
needs to be a large amount of other work to fix this handling of
lumpy-pgo-release properly, so in the meantime, the old form of breakage
(scheduling against lumpy-release when we see lumpy-pgo-release) is
actually preferable.
This reverts commit c3d4b7950036abb6c89f884d529c8d8839e23eed
Change-Id: Id0d352c56560f6baccf719dc766072cee904d6e6
Reviewed-on: https://gerrit.chromium.org/gerrit/44544
Commit-Queue: Alex Miller <milleral@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
Tested-by: Alex Miller <milleral@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|
| c3d4b7950036abb6c89f884d529c8d8839e23eed |
|
01-Mar-2013 |
Alex Miller <milleral@chromium.org> |
[autotest] Schedule tests against lumpy-pgo-release builds.
We currently see lumpy-pgo-release builds, and then schedule tests
against lumpy-release. This CL changes the parsing so that we see
pgo-release as a build config type, and then schedule tests against
lumpy-pgo-release as one would expect.
Note that it took a local modification to base_event.ParseBuildName in
order for a local run of suite_scheduler to work. This will get fixed
once a standardized fully parseable naming convention is agreed upon.
BUG=chromium-os:39283
TEST=unit
forced event locally and watched lumpy-pgo-release get scheduled
Change-Id: Ic9dba31e58d342b593a7d84f605bddfb77a81d9c
Reviewed-on: https://gerrit.chromium.org/gerrit/44366
Tested-by: Alex Miller <milleral@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|
| cdcc0ee70346096cbc88b2bef20daab1cb0dc4d6 |
|
27-Feb-2013 |
Alex Miller <milleral@chromium.org> |
[autotest] Teach suite_scheduler how to parse pgo canaries.
No one had previously named something <board>-<something>-release,
therefore, we have no idea how to deal with this.
BUG=chromium-os:39283
TEST=unit
Change-Id: I44ff745a35ebf0890d881b6c03dc8f5ce3df0016
Reviewed-on: https://gerrit.chromium.org/gerrit/44136
Tested-by: Alex Miller <milleral@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
Commit-Queue: Alex Miller <milleral@chromium.org>
Reviewed-by: Alex Miller <milleral@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|
| 28424c52f29f690c2dfa2a6c4d649f25edfada11 |
|
14-May-2012 |
Chris Masone <cmasone@chromium.org> |
[autotest] Make suite scheduler ssh commands stop logging to stderr
BUG=chromium-os:29808
TEST=unit
TEST=run the scheduler with a --log-dir, note that ssh command output is no
TEST=longer printing in the foreground, but being logged at the DEBUG level.
STATUS=Fixed
Change-Id: Id5fa5256d5901d7c3c463667fde2233aab8f6ec2
Reviewed-on: https://gerrit.chromium.org/gerrit/22615
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|
| b75d541c9e035df26adc38ed233fdd87cb2cff08 |
|
01-May-2012 |
Chris Masone <cmasone@chromium.org> |
[autotest] suite_scheduler.py should tolerate bad 'board' values
If we get a 'board' from the AFE that doesn't jive with the builds we
know about from manifest-versions.git, the scheduler should not die.
Instead, it should be able to detect this, log it, and roll on.
BUG=chromium-os:30280
TEST=unit
TEST=run the scheduler against an AFE that has board:non_existent as a label; the scheduler should not fail.
Change-Id: I648845aa7ac58f2de7b2ff91c5bf0a369372bac9
Reviewed-on: https://gerrit.chromium.org/gerrit/21510
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Scott Zawalski <scottz@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|
| bb3388570efebf3f3d07b9d71238190ce9fe0088 |
|
20-Apr-2012 |
Chris Masone <cmasone@chromium.org> |
[autotest] Fix bugs in ManifestVersions.Update()
--git-dir works fine on its own, if you're just querying git state.
Once you start updating it (as with git pull and such), you need --work-tree
as well, or git tries to use the CWD as the root of your working directory.
Which isn't good.
BUG=chromium-os:27586
TEST=unit
TEST=./suite_scheduler.py -f suite_scheduler_test.ini; the scheduler should make it through several iterations of the main loop without barfing on git pull
Change-Id: I8d122e3731dc34c92db730fef97877641bb3d983
Reviewed-on: https://gerrit.chromium.org/gerrit/20726
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|
| 93f51d4da152538007d5b44a2dc9d2bbb1fe3429 |
|
18-Apr-2012 |
Chris Masone <cmasone@chromium.org> |
[autotest] Add BuildEvent and derived NewBuild event class
The NewBuild event will allow us to Run() tasks whenever a new build appears
for a supported board.
BUG=chromium-os:27586
TEST=unit
Change-Id: I3432ecde38397fde6e0d7d675bf302a796c117f5
Reviewed-on: https://gerrit.chromium.org/gerrit/20524
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|
| 9273c0ddfcdd07a298c2145270d7bf8cb9865e23 |
|
13-Apr-2012 |
Chris Masone <cmasone@chromium.org> |
[autotest] Fix path-globbing bug in ManifestVersions
As of this CL, I'm able to do an end-to-end test and see suites
get scheduled on my local AFE.
Also added a mechanism to config an event to fire every time the
scheduler loops back around, for testing purposes.
BUG=chromium-os:27586
TEST=unit
TEST=create a config with an event that will run_on=nightly, and a [nightly_params] section with always_fire: True
Change-Id: Ib09e3eeac06ef3eae341434aa465b6bd1d9c8afb
Reviewed-on: https://gerrit.chromium.org/gerrit/20251
Commit-Ready: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
Tested-by: Chris Masone <cmasone@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|
| 5bde7dc7d8b0608feb43491d5ac648d11c890f54 |
|
10-Apr-2012 |
Chris Masone <cmasone@chromium.org> |
[autotest] Add, and begin using, ManifestVersions class.
This CL creates the ManifestVersons class, to enable other
componenets to query info from the manifest-versions git repo.
Abstracts away all git operations from consumers.
Also introduces some basic usage of the class, to discover new manifests that
appeared in a given time frame (used by Nightly and Weekly classes).
BUG=chromium-os:27586
TEST=unit
Change-Id: I07e707112fcca8279b37a5ce4ba2b54a8e150889
Reviewed-on: https://gerrit.chromium.org/gerrit/19867
Tested-by: Chris Masone <cmasone@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Commit-Ready: Chris Masone <cmasone@chromium.org>
/external/autotest/site_utils/suite_scheduler/manifest_versions_unittest.py
|