1[AUTOTEST_WEB] 2# IP == cautotest-mysql, see http://crosbug.com/38773 3# TODO(milleral): Switch back to DNS name when bug is fixed 4# master db: chromeos-server25.mtv 5host: 172.24.26.45 6database: chromeos_autotest_db 7db_type: mysql 8user: chromeosqa-admin 9password: USE SHADOW PASSWORD 10job_timeout_default: 24 11job_timeout_mins_default: 1440 12job_max_runtime_mins_default: 1440 13parse_failed_repair_default: 0 14# Only set this if your server is not 'http://[SERVER] hostname/afe/' 15#base_url: http://your_autotest_server/afe/ 16# IP == cautotest-mysql, see http://crosbug.com/38773 17readonly_host: 172.24.26.45 18readonly_user: chromeosqa-read 19readonly_password: qyBM6kDu 20query_timeout: 3600 21min_retry_delay: 20 22max_retry_delay: 60 23graph_cache_creation_timeout_minutes: 10 24parameterized_jobs: False 25# Whether to enable django template debug mode. If this is set to True, all 26# django errors will be wrapped in a nice debug page with detailed environment 27# and stack trace info. Turned off by default. 28template_debug_mode: True 29# Whether to enable django SQL debug mode. If this is set to True, all 30# queries performed by the Object Relational Mapper subsystem will be printed, 31# which means the scheduler logs will contains all the queries executed. This 32# is too much verbosity for 'production' systems, hence turned off by default. 33sql_debug_mode: False 34 35# Restricted user group. The users in the specified groups only have 36# access to master server. Will always direct them to google storage for logs 37# rather than drones or shards. 38restricted_groups: USE SHADOW RESTRICTED_GROUPS 39 40# The tko parser will use these database settings. 41# This is for sharding: Even when sharding, the results (tko tables) should 42# still be written to the master database. 43global_db_host: 44global_db_database: 45global_db_type: 46global_db_user: 47global_db_password: 48global_db_query_timeout: 49global_db_min_retry_delay: 50global_db_max_retry_delay: 51 52[AUTOTEST_SERVER_DB] 53# Server database setting. Fall back to use AFE database settings. 54database: chromeos_lab_servers 55 56[SHARD] 57# If this is not None, the instance is considered a shard. 58# The value should be the hostname of the local shard. 59shard_hostname: 60heartbeat_pause_sec: 60 61 62[AUTOSERV] 63# Autotest potential install paths 64client_autodir_paths: /usr/local/autotest,/usr/local/autodir 65# White list of tests with run time measurement enabled. 66measure_run_time_tests: desktopui_ScreenLocker,login_LoginSuccess,security_ProfilePermissions 67# Incrementally update TKO with the status as the test runs. 68incremental_tko_parsing: False 69# If True, autoserv won't interact with real devices. 70# It will sleep 10 seconds and then pass successfully. 71testing_mode: False 72 73# Directory stores LXC containers 74container_path: /usr/local/autotest/containers 75# Download link for base image of container 76container_base: http://storage.googleapis.com/chromeos-image-archive/autotest-containers/base.tar.xz 77# Enable server-side package using container 78# TODO(dshi): Change this to True after SSP via container is rolled out. 79enable_ssp_container: False 80 81# Minimum OS version that supports server side packaging. Older builds may 82# not have server side package built or with Autotest code change to support 83# server-side packaging. 84min_version_support_ssp: 6986 85 86# Set to True to allow servod to be started automatically in Moblab. 87auto_start_servod: False 88 89[CLIENT] 90drop_caches: False 91drop_caches_between_iterations: False 92# Specify an alternate location to store the test results 93#output_dir: /var/log/autotest/ 94output_dir: 95#wireless_ssid: SEE SHADOW CONFIG 96#wireless_password: SEE SHADOW CONFIG 97#wireless_security: SEE SHADOW CONFIG 98# The zone that all Chrome OS devices are in if they are in a lab. 99dns_zone: cros.corp.google.com 100# If necessary, specify a proxy for client downloads 101http_proxy: 102https_proxy: 103 104# Index to upload metadata to. 105metadata_index: 106 107[SERVER] 108hostname: cautotest 109# Turn on RPC Logging 110rpc_logging: False 111# Note the user that is running the webserver has to be able to write 112# to the below directory/file otherwise the frontend will not work with logging 113rpc_log_path: /usr/local/autotest/logs/rpcserver.log 114# Number of old logs to keep around 115rpc_num_old_logs: 5 116rpc_max_log_size_mb: 20 117# Transfer RPC logs to a RPC logging server 118rpc_logserver: False 119# Minimum amount of disk space required for AutoTest in GB 120gb_diskspace_required: 0.7 121# Minmum number of i-nodes for stateful, in 1000 i-node units. 122kilo_inodes_required: 100 123# Rialto has a small disk size, so reduce the required inodes for it. 124# See https://code.google.com/p/chrome-os-partner/issues/detail?q=45875 125kilo_inodes_required_veyron_rialto: 55 126kilo_inodes_required_arkham: 50 127kilo_inodes_required_storm: 50 128kilo_inodes_required_whirlwind: 50 129 130# Minimum amount of disk space required for encrypted stateful partition in GB 131gb_encrypted_diskspace_required: 0.1 132# If for some reason you don't want to rely on the Mail Transport Agent 133# installed on this machine, you can provide an SMTP server directly here. 134# If none provided, defaults to 'localhost', which tries to use the MTA 135# configured on the machine to send the messages. 136smtp_server: 137smtp_port: 138smtp_user: 139smtp_password: 140# Time in hours to wait before giving up on crash collection. 141crash_collection_hours_to_wait: 0.001 142 143# If True, use autotest_server_db to verify the host before running services 144# like scheduler, host-scheduler and suite-scheduler. 145use_server_db: False 146 147# Suite scheduler afe server 148# If no specified, will default to [SERVER]: hostname 149suite_scheduler_afe: 150 151# AFE server connected to the master DB. 152global_afe_hostname: cautotest 153 154# Credential directory where all credentials files should go. If not specified, 155# will look for credentils in autotest root dir. 156creds_dir: 157 158[SCHEDULER] 159die_on_orphans: False 160enable_scheduler: True 161notify_email: chromeos-test-cron+cautotest@google.com 162notify_email_errors: USE SHADOW NOTIFY_EMAIL_ERRORS 163notify_email_from: chromeos-autotest@google.com 164notify_email_statuses: Completed,Failed,Aborted 165max_processes_per_drone: 1000 166max_processes_warning_threshold: 0.8 167max_parse_processes: 100 168max_transfer_processes: 50 169tick_pause_sec: 5 170minimum_tick_sec: 0.5 171clean_interval_minutes: 5 172drones: SET IN SHADOW CONFIG 173drone_installation_directory: /usr/local/autotest 174results_host: localhost 175results_host_installation_directory: 176secs_to_wait_for_atomic_group_hosts: 600 177pidfile_timeout_mins: 300 178max_pidfile_refreshes: 2000 179gc_stats_interval_mins: 360 180# set nonzero to enable periodic reverification of all dead hosts 181reverify_period_minutes: 30 182reverify_max_hosts_at_once: 30 183drone_sets_enabled: False 184# default_drone_set_name: This is required if drone sets are enabled. 185default_drone_set_name: 186# Disable archiving by default. 187enable_archiving: False 188copy_task_results_back: False 189copy_parse_log_back: False 190tick_debug: True 191extra_debugging: False 192# max_repair_limit sets how many times a single HQE will go through 193# repairing -> requeued -> fail -> repairing 194max_repair_limit: 2 195max_provision_retries: 0 196drone_build_externals: False 197inline_host_acquisition: USE SHADOW INLINE_HOST_ACQUISITION 198# If True, the drone manager creates a thread for each drone. 199# Otherwise, drones are handled in a single thread. 200threaded_drone_manager: True 201 202[HOSTS] 203wait_up_processes: 204default_protection: NO_PROTECTION 205# Time in seconds to wait for a machine to come back after reboot. 206default_reboot_timeout: 240 207# Time in seconds to wait for a machine to go down prior to reboot. 208wait_down_reboot_timeout: 120 209# Time in seconds to wait before generating a warning if a host has not gone 210# down for reboot. 211wait_down_reboot_warning: 30 212# Time in hours to wait for a host to recover after a down state. 213hours_to_wait_for_recovery: 0.01 214 215[AUTOSERV] 216# Autotest has 2 implementations of SSH based hosts, the default (raw_ssh), and 217# another one based on the python SSH library paramiko (paramiko). 218# You can change the default 'raw_ssh' to 'paramiko' if you want to. 219ssh_engine: raw_ssh 220# Set to True to take advantage of OpenSSH-based connection sharing. This would 221# have bigger performance impact when ssh_engine is 'raw_ssh'. 222enable_master_ssh: True 223# Autotest server operators *really should* set this to True, specially if 224# using ssh_engine 'paramiko'. 225require_atfork_module: False 226# Set to False to disable ssh-agent usage with paramiko 227use_sshagent_with_paramiko: True 228enable_server_prebuild: False 229 230[PACKAGES] 231# in days 232custom_max_age: 1 233# in Gigabyte 234minimum_free_space: 1 235serve_packages_from_autoserv: True 236 237[CROS] 238# If afe_stable_versions table does not have the stable version for a given 239# board and there is no entry of board `DEFAULT`, following value defined in 240# stable_cros_version will be used as the stable CrOS version. 241# Use `cli/atest stable_version` command to view or manage stable versions. 242# WARNING! Edit following setting will NOT work if stable versions are stored 243# in afe_stable_versions table already! 244stable_cros_version: R46-7390.59.0 245stable_build_pattern: %s-release/%s 246source_tree: /usr/local/google/chromeos 247gs_offloading_enabled: True 248image_storage_server: gs://chromeos-image-archive/ 249results_storage_server: gs://chromeos-autotest-results/ 250# dev_server_hosts is the list of all servers running a devserver instance 251# (regardless of CrashServer/ImageServer/etc.) that should be considered for 252# monitoring/deploy actions. You should very likely keep this list in sync with 253# `dev_server` and `crash_server` unless you're very temporarily pulling a 254# server out of rotation. 255dev_server_hosts: chromeos-devserver1, chromeos-devserver2, chromeos-devserver3, chromeos-devserver4, chromeos-devserver5, chromeos-devserver6, chromeos-devserver7, chromeos-crash1, chromeos2-devserver6, chromeos2-devserver7, chromeos2-devserver5 256dev_server: http://172.17.40.27:8082, http://100.107.160.1:8082, http://100.107.160.2:8082, http://172.17.40.17:8082, http://172.17.40.20:8082, http://172.17.40.19:8082, http://100.107.160.3:8082, http://100.107.160.4:8082, http://172.17.40.22:8082, http://100.107.160.7:8082 257canary_channel_server: gs://chromeos-releases/canary-channel/ 258# chromeos-crash1.cros 259crash_server: http://172.17.40.24:8082, http://100.107.160.5:8082, http://100.107.160.6:8082 260sharding_factor: 1 261infrastructure_user: chromeos-test 262gs_offloader_use_rsync: False 263 264# Naming convention of Android build. 265android_build_name_pattern: %\(branch\)s/%\(target\)s/%\(build_id\)s 266 267firmware_url_pattern: %s/static/%s/firmware_from_source.tar.bz2 268factory_image_url_pattern: %s/static/canary-channel/%s/factory_test/chromiumos_factory_image.bin 269factory_artifact: factory_image 270image_url_pattern: %s/update/%s 271log_url_pattern: http://%s/tko/retrieve_logs.cgi?job=/results/%s/ 272package_url_pattern: %s/static/%s/autotest/packages 273servo_board: beaglebone_servo 274 275# Username and password for connecting to remote power control switches of 276# the "Sentry Switched CDU" type 277rpm_sentry_username: fake_user 278rpm_sentry_password: fake_password 279rpm_frontend_uri: http://chromeos-rpmserver1.cbf.corp.google.com:9999 280rpm_recovery_boards: stumpy,kiev 281 282# Path the devserver source tree, used for spawning devserver from autoserv in 283# some of the tests. Please override in local shadow config file. 284#devserver_dir: /path/to/src/platform/dev 285 286lab_status_url: http://chromiumos-lab.appspot.com/current?format=json 287 288# statsd server feeding Graphite (swift-capsule-791 GCE project) 289STATSD_SERVER: 146.148.70.158 290STATSD_PORT: 8125 291 292 293sam_instances: cautotest 294test_instance: chromeos-autotest.cbf 295extra_servers: chromeos-mcp 296 297# ES_HOST's hostname is chromeos-lab-graphite.cbf.corp.google.com 298# This es server is used for testing purposes only. 299ES_HOST: 172.25.61.45 300ES_PORT: 9200 301ES_UDP_PORT: 9700 302ES_USE_HTTP: False 303 304skip_devserver_health_check: True 305 306# The swarming instance that will be used for golo proxy 307swarming_proxy: 308 309# Limit the number of files in the result folder. 310gs_offloader_limit_file_count: False 311 312# A list of pools that allow to be repaired using firmware repair. 313pools_support_firmware_repair: faft-test,faft-test-tot,faft-test-experiment 314 315# A list of restricted subnets, in the format of ip:mask_bits, e.g., 10.0.0.1:24 316restricted_subnets: 317 318# Flags to enable/disable devserver and drone election in resctricted subnet. 319enable_drone_in_restricted_subnet: False 320enable_devserver_in_restricted_subnet: False 321 322# Set to True for test to prefer devserver in the same subnet. 323prefer_local_devserver: False 324 325[BUG_REPORTING] 326gs_domain: https://storage.cloud.google.com/ 327chromeos_image_archive: chromeos-image-archive/ 328arg_prefix: ?arg= 329retrieve_logs_cgi: http://cautotest.corp.google.com/tko/retrieve_logs.cgi?job=/ 330generic_results_bin: results/ 331debug_dir: debug/ 332buildbot_builders: http://chromegw.corp.google.com/i/chromeos/builders/ 333build_prefix: build/ 334job_view = http://%s/afe/#tab_id=view_job&object_id=%s 335tracker_url: https://code.google.com/p/chromium/issues/detail?id= 336gs_file_prefix: gs:// 337chromium_email_address = @chromium.org 338credentials: USE SHADOW CREDENTIALS 339client_id: USE SHADOW CLIENT_ID 340client_secret: USE SHADOW CLIENT_SECRET 341scope: USE SHADOW SCOPE 342wmatrix_retry_url: https://wmatrix.googleplex.com/retry_teststats/?days_back=30&tests=%s 343 344 345[NOTIFICATIONS] 346chromium_build_url: http://build.chromium.org/p/chromiumos/ 347sheriffs: USE SHADOW SHERIFFS 348lab_sheriffs: USE SHADOW SHERIFFS 349gmail_api_credentials: 350gmail_api_credentials_test_failure: 351 352 353[POOL_INSTANCE_SHARDING] 354# Add a mapping of `pool_name: server` to your shadow config to have run_suite 355# send all of the suites for pool to the specified server. 356 357[UPDATE_COMMANDS] 358afe: AUTOTEST_REPO/utils/compile_gwt_clients.py -c autotest.AfeClient 359apache: sudo service apache2 reload 360build_externals: AUTOTEST_REPO/utils/build_externals.py 361migrate: AUTOTEST_REPO/database/migrate.py sync 362test_importer: AUTOTEST_REPO/utils/test_importer.py 363tko: AUTOTEST_REPO/utils/compile_gwt_clients.py -c autotest.TkoClient 364 365# [UPDATE] 366# Set this with command names that should run after every update. 367# commands: build_externals test_importer etc 368# Set this with service names that should be restarted after every update. 369# services: 370 371[SSP] 372# Section for configuration needed for server-side packaging. 373# User that runs the autoserv process in the host of the container. 374# The user is passed to a container through global config file so a process 375# running inside the container can use the same user to make RPC. 376user: 377 378[ACTS] 379# Section for ACTS configuration. 380acts_config_folder: 381 382[ANDROID] 383image_url_pattern: %s/static/%s 384stable_version_dragonboard: git_mnc-brillo-dev/dragonboard-userdebug/2512766 385