Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1)

Issue 3156047: modify factory_Wipe to fit into new flow (with factory_Verify) (Closed)

Created:
10 years, 4 months ago by Hung-Te
Modified:
9 years, 7 months ago
Reviewers:
Tammo Spalink
CC:
chromium-os-reviews_chromium.org, sosa+cc_chromium.org, seano, ericli, petkov+cc_chromium.org
Visibility:
Public.

Description

modify factory_Wipe to fit into new flow (with factory_Verify) The factory_Wipe now only depends on the factory_Verify test, which can be assigned via unique_name in suite_Factory/test_list. Ref: http://codereview.chromium.org/3180022/show BUG=chrome-os-partner:827 TEST=manual Change-Id: Icc9f84ee7aa0842de8075b4c94c79e0c9a7026bd

Patch Set 1 #

Total comments: 5

Patch Set 2 : fix as reviewer suggeted #

Unified diffs Side-by-side diffs Delta from patch set Stats (+17 lines, -77 lines) Patch
M client/bin/factory.py View 1 2 chunks +7 lines, -0 lines 0 comments Download
M client/site_tests/factory_Wipe/factory_Wipe.py View 1 2 chunks +9 lines, -74 lines 0 comments Download
M client/site_tests/factory_Wipe/force_run View 1 chunk +1 line, -3 lines 0 comments Download

Messages

Total messages: 5 (0 generated)
Hung-Te
10 years, 4 months ago (2010-08-24 13:01:47 UTC) #1
Tammo Spalink
http://codereview.chromium.org/3156047/diff/1/2 File client/bin/factory.py (right): http://codereview.chromium.org/3156047/diff/1/2#newcode40 client/bin/factory.py:40: def check_ready_for_finalize(need_verify, test_list, status_file_path): not sure i understand why ...
10 years, 4 months ago (2010-08-25 03:26:01 UTC) #2
Hung-Te
Right now only factory_Wipe needs that. But in the future if we put more stuff ...
10 years, 4 months ago (2010-08-25 03:48:10 UTC) #3
Tammo Spalink
http://codereview.chromium.org/3156047/diff/1/2 File client/bin/factory.py (right): http://codereview.chromium.org/3156047/diff/1/2#newcode32 client/bin/factory.py:32: FINAL_VERIFY_TEST_NAME = 'factory_Verify' how about FINAL_VERIFICATION_TEST_UNIQUE_NAME? http://codereview.chromium.org/3156047/diff/1/2#newcode45 client/bin/factory.py:45: if ...
10 years, 4 months ago (2010-08-25 04:03:42 UTC) #4
Hung-Te
10 years, 4 months ago (2010-08-25 04:51:21 UTC) #5
http://codereview.chromium.org/3156047/diff/1/2
File client/bin/factory.py (right):

http://codereview.chromium.org/3156047/diff/1/2#newcode32
client/bin/factory.py:32: FINAL_VERIFY_TEST_NAME = 'factory_Verify'
On 2010/08/25 04:03:42, Tammo Spalink wrote:
> how about FINAL_VERIFICATION_TEST_UNIQUE_NAME?

Done.

http://codereview.chromium.org/3156047/diff/1/2#newcode45
client/bin/factory.py:45: if status_map.lookup_status(xtest) != PASSED:
Since there's only one (wipe) test needs this now, I'd agree to change as you
suggested.

Powered by Google App Engine
This is Rietveld 408576698