New issue
Advanced search Search tips

Issue 916065 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Jan 15
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Feature



Sign in to add a comment

Chromeperf-created bugs should be created with status Unconfirmed

Project Member Reported by hablich@chromium.org, Dec 18

Issue description

Chromeperf-created bugs should be created with status Unconfirmed instead of Untriaged. This would much better reflect the state of things. Bisect very often fails to confirm the reported regression. This means that Untriaged (which indicates that the bug is confirmed) is wrong.


 
Cc: sullivan@chromium.org
Cc: benjhayden@chromium.org
Components: -Speed>Bisection Speed>Dashboard
Owner: seanmccullough@chromium.org
Assigning to seanmccullough for triage.
Cc: dtu@chromium.org seanmccullough@chromium.org
Owner: benjhayden@chromium.org
Status: Started (was: Untriaged)
1-line fix on the way.
Thanks!
Project Member

Comment 5 by bugdroid1@chromium.org, Dec 21

The following revision refers to this bug:
  https://chromium.googlesource.com/catapult/+/2f6c18c2d5aa3e4bb9dc13836711429c63071072

commit 2f6c18c2d5aa3e4bb9dc13836711429c63071072
Author: benshayden <benjhayden@chromium.org>
Date: Fri Dec 21 00:18:28 2018

Create bugs Unconfirmed by default instead of Untriaged.

Bug:  chromium:916065 
Change-Id: I8f52da7822cba6260a1f7f4669a18e5c6ef49758
Reviewed-on: https://chromium-review.googlesource.com/c/1382992
Reviewed-by: Sean McCullough <seanmccullough@chromium.org>
Reviewed-by: Dave Tu <dtu@chromium.org>
Commit-Queue: Ben Hayden <benjhayden@chromium.org>

[modify] https://crrev.com/2f6c18c2d5aa3e4bb9dc13836711429c63071072/dashboard/dashboard/services/issue_tracker_service_test.py
[modify] https://crrev.com/2f6c18c2d5aa3e4bb9dc13836711429c63071072/dashboard/dashboard/services/issue_tracker_service.py

I'll keep this open until we deploy.
Project Member

Comment 7 by bugdroid1@chromium.org, Dec 21

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a0b857cf5883dc1192f698d0f9daffddd8dcf3e6

commit a0b857cf5883dc1192f698d0f9daffddd8dcf3e6
Author: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Date: Fri Dec 21 02:39:25 2018

Roll src/third_party/catapult 08027af50264..2f6c18c2d5aa (1 commits)

https://chromium.googlesource.com/catapult.git/+log/08027af50264..2f6c18c2d5aa


git log 08027af50264..2f6c18c2d5aa --date=short --no-merges --format='%ad %ae %s'
2018-12-21 benjhayden@chromium.org Create bugs Unconfirmed by default instead of Untriaged.


Created with:
  gclient setdep -r src/third_party/catapult@2f6c18c2d5aa

The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel

BUG= chromium:916065 
TBR=sullivan@chromium.org

Change-Id: I2a85269f55e5e0bc11771ac4585449cf24a15a33
Reviewed-on: https://chromium-review.googlesource.com/c/1387683
Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#618437}
[modify] https://crrev.com/a0b857cf5883dc1192f698d0f9daffddd8dcf3e6/DEPS

Status: Fixed (was: Started)
This is deployed.

Sign in to add a comment