afe_jobs has at least 4 concepts of timeout |
|||
Issue descriptionChrome Version: (copy from chrome://version) OS: (e.g. Win7, OSX 10.9.5, etc...) What steps will reproduce the problem? (1) (2) (3) What is the expected result? What happens instead? Please use labels and text to provide additional information. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report. mysql> describe afe_jobs; +----------------------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +----------------------+--------------+------+-----+---------+----------------+ | id | int(11) | NO | PRI | NULL | auto_increment | | owner | varchar(255) | YES | MUL | NULL | | | name | varchar(255) | YES | MUL | NULL | | | priority | int(11) | YES | | NULL | | | control_file | text | YES | | NULL | | | control_type | int(11) | YES | | NULL | | | created_on | datetime | YES | MUL | NULL | | | synch_count | int(11) | NO | | NULL | | | timeout | int(11) | NO | | NULL | | | run_verify | tinyint(1) | YES | | 1 | | | email_list | varchar(250) | NO | | NULL | | | reboot_before | smallint(6) | NO | | NULL | | | reboot_after | smallint(6) | NO | | NULL | | | parse_failed_repair | tinyint(1) | NO | | 1 | | | max_runtime_hrs | int(11) | NO | | NULL | | | drone_set_id | int(11) | YES | MUL | NULL | | | parameterized_job_id | int(11) | YES | MUL | NULL | | | max_runtime_mins | int(11) | NO | | NULL | | | parent_job_id | int(11) | YES | MUL | NULL | | | test_retry | int(11) | NO | | 0 | | | run_reset | smallint(6) | NO | | 1 | | | timeout_mins | int(11) | NO | | NULL | | | shard_id | int(11) | YES | MUL | NULL | | | require_ssp | tinyint(1) | YES | | NULL | | +----------------------+--------------+------+-----+---------+----------------+ 24 rows in set (0.00 sec) timeout, max_runtime_hrs, max_runtime_mins, timeout_mins I'm pretty sure that at least max_runtime_mins and timeout are used (I see them both referenced in monitor_db_cleanup.py) but not sure of the others.
,
Jun 1 2017
c#1: That was my reading along with the same uncertainties regarding started_on.
,
Jun 12 2017
1. document this 2. investigate re-naming obsolete columns (Don thinks it can be done) as long as the callers don't use the names
,
Jun 12 2017
Details on renaming columns: https://dba.stackexchange.com/questions/53836/how-long-will-it-take-to-rename-table
,
Dec 20 2017
This bug is not really actionable. Moved its discoveries to doc at https://sites.google.com/a/google.com/chromeos/for-team-members/infrastructure/backend/timeouts-in-autotest |
|||
►
Sign in to add a comment |
|||
Comment 1 by akes...@chromium.org
, Jun 1 2017