Which bug tracker to use

5 views
Skip to first unread message

Caleb Rouleau

unread,
Dec 22, 2017, 5:21:34 PM12/22/17
to benchmar...@chromium.org, speed-ser...@chromium.org
I have been noticing that sometimes Catapult devs like Ned file bugs like this one for Catapult code in the Chromium bug tracker. I can see how this is nice since those bugs can be blocked on, mark duplicate, etc from other Chromium bugs. But I also see the github issue tracker in use. Which one is preferred and in which cases? Would it be easier to switch to the Chromium tracker for all new bugs?


Thanks,
--
Caleb Rouleau
Chrome Test Infrastructure

Charlie Andrews

unread,
Jan 2, 2018, 1:07:06 PM1/2/18
to Caleb Rouleau, benchmar...@chromium.org, speed-ser...@chromium.org
Hey Caleb,

Sorry, this is a strange artifact of being in the middle of a migration. I think that, at this point, all Telemetry bugs should be filed under monorail under Speed > Telemetry. I'm not sure about trace viewer bugs.

It used to be that Chromium-side bugs (i.e. related to specific benchmarks or the Google-specific infrastructure that runs them) should be filed in monorail, whereas Telemetry and trace-viewer side bugs should be filed on Github. We're moving away from using the Github issue tracker though into a monorail-only world, so I think at this point everything should be monorail only. That's my understanding, at least.

--
You received this message because you are subscribed to the Google Groups "Chrome benchmarking" group.
To unsubscribe from this group and stop receiving emails from it, send an email to benchmarking-dev+unsubscribe@chromium.org.
To post to this group, send email to benchmar...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/benchmarking-dev/CAJRtWzFKG3bDhCiPxtcPHDo65EiC4H%2BuKNntBWGq6tgMp25HKw%40mail.gmail.com.



--

Charlie Andrews | Software Engineer | char...@google.com
 

Ned

unread,
Jan 2, 2018, 1:12:17 PM1/2/18
to Charlie Andrews, Caleb Rouleau, benchmar...@chromium.org, speed-ser...@chromium.org
+1 to what Charlie says. Sorry for your confusion, we will be migrate all github issues that are still relevant to " Speed > Telemetry" component.

On Tue, Jan 2, 2018 at 1:07 PM 'Charlie Andrews' via Chrome benchmarking <benchmar...@chromium.org> wrote:
Hey Caleb,

Sorry, this is a strange artifact of being in the middle of a migration. I think that, at this point, all Telemetry bugs should be filed under monorail under Speed > Telemetry. I'm not sure about trace viewer bugs.

It used to be that Chromium-side bugs (i.e. related to specific benchmarks or the Google-specific infrastructure that runs them) should be filed in monorail, whereas Telemetry and trace-viewer side bugs should be filed on Github. We're moving away from using the Github issue tracker though into a monorail-only world, so I think at this point everything should be monorail only. That's my understanding, at least.
On Fri, Dec 22, 2017 at 5:21 PM, 'Caleb Rouleau' via Chrome benchmarking <benchmar...@chromium.org> wrote:
I have been noticing that sometimes Catapult devs like Ned file bugs like this one for Catapult code in the Chromium bug tracker. I can see how this is nice since those bugs can be blocked on, mark duplicate, etc from other Chromium bugs. But I also see the github issue tracker in use. Which one is preferred and in which cases? Would it be easier to switch to the Chromium tracker for all new bugs?


Thanks,
--
Caleb Rouleau
Chrome Test Infrastructure

--
You received this message because you are subscribed to the Google Groups "Chrome benchmarking" group.
To unsubscribe from this group and stop receiving emails from it, send an email to benchmarking-d...@chromium.org.

To post to this group, send email to benchmar...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/benchmarking-dev/CAJRtWzFKG3bDhCiPxtcPHDo65EiC4H%2BuKNntBWGq6tgMp25HKw%40mail.gmail.com.
--

Charlie Andrews | Software Engineer | char...@google.com
 

--
You received this message because you are subscribed to the Google Groups "Chrome benchmarking" group.
To unsubscribe from this group and stop receiving emails from it, send an email to benchmarking-d...@chromium.org.

To post to this group, send email to benchmar...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/benchmarking-dev/CAPTbymeC-h6Vv1SnbzUuqr-GrHaWaUkCnhGs%3DRR243%2BmySTFBQ%40mail.gmail.com.

Caleb Rouleau

unread,
Feb 22, 2019, 1:00:40 AM2/22/19
to Ned, Charlie Andrews, benchmar...@chromium.org, speed-ser...@chromium.org
Reply all
Reply to author
Forward
0 new messages