Page URL: https://13850-8d17315-dot-waterfall-frontend-dot-findit-for-me.appspot.com/waterfall/flake?key=ag9zfmZpbmRpdC1mb3ItbWVyqAELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCJyY2hyb21pdW0uY2hyb21pdW1vcy9saW51eC1jaHJvbWVvcy1kYmcvNDA1OS9icm93c2VyX3Rlc3RzL1ZtbGtaVzlRYkdGNVpYSkNjbTkzYzJWeVZHVnpkQzVEYkdsamEwTnZiblJ5YjJ4Q2RYUjBiMjV6DAsSE01hc3RlckZsYWtlQW5hbHlzaXMYAgw

 Description:
This admin-triggered analysis still runs Swarming task in 150. This could cause delayed analysis result for our deploy at 10:30am, but set default at 4pm (this happened last week). Today, the issue is a separate bug https://bugs.chromium.org/p/chromium/issues/detail?id=809219
We'd better to set it at the same priority as CQ try-jobs.

(For waterfall test failures, the Swarming task result is reused, but we need to make some change as well. That is a separate issue.)