* Re: [regression] Kernel OOPS on boot with Kernel 6.3(.1) and RTL8153 Gigabit Ethernet Adapter [not found] ` <9284a9ec-d7c9-68e8-7384-07291894937b@leemhuis.info> @ 2023-05-08 20:09 ` Jakub Kicinski 2023-05-11 13:25 ` Thorsten Leemhuis 0 siblings, 1 reply; 3+ messages in thread From: Jakub Kicinski @ 2023-05-08 20:09 UTC (permalink / raw) To: Linux regression tracking (Thorsten Leemhuis) Cc: Linux regressions mailing list, Bjørn Mork, Hayes Wang, netdev, Paolo Abeni, Eric Dumazet, David S. Miller, Stanislav Fomichev, workflows On Sat, 6 May 2023 08:20:23 +0200 Linux regression tracking (Thorsten Leemhuis) wrote: > > I don't seem to have the permissions on BZ, but I'm guessing we could > > do the opposite - you could flip bugbot on first to have it flush the BZ > > report to the list, and then reply on the list with regzbot tracking? > > That's the plan for the future, but for now I don't want to do that, as > it might mess up other peoples workflows, as hinted above already and > discussed here: > > https://lore.kernel.org/all/1f0ebf13-ab0f-d512-6106-3ebf7cb372f1@leemhuis.info/ > > That was only recently, but if you jump in there as well it might > persuade Konstantin to enable bugbot for other products/components. Then > I could and would do what you suggested. CC: workflows I'm a bit confused. I understand that we don't want to automatically send all bugzilla reports to the ML. But AFAIU this is to avoid spamming the list / messing with people's existing BZ workflow. If you pre-triage the problem and decide to forward it to the list - whether you do it with buzbot + regzbot or manual + regzbot is moot. The bugbot can be enabled per BZ entry (AFAIU), so you can flip it individually for the thread you want to report. It should flush that BZ to the list. At which point you can follow your normal ML regression process. Where did I go off the rails? ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [regression] Kernel OOPS on boot with Kernel 6.3(.1) and RTL8153 Gigabit Ethernet Adapter 2023-05-08 20:09 ` [regression] Kernel OOPS on boot with Kernel 6.3(.1) and RTL8153 Gigabit Ethernet Adapter Jakub Kicinski @ 2023-05-11 13:25 ` Thorsten Leemhuis 2023-05-11 16:06 ` Konstantin Ryabitsev 0 siblings, 1 reply; 3+ messages in thread From: Thorsten Leemhuis @ 2023-05-11 13:25 UTC (permalink / raw) To: Jakub Kicinski Cc: Linux regressions mailing list, Bjørn Mork, Hayes Wang, netdev, Paolo Abeni, Eric Dumazet, David S. Miller, Stanislav Fomichev, workflows, Konstantin Ryabitsev On 08.05.23 22:09, Jakub Kicinski wrote: > On Sat, 6 May 2023 08:20:23 +0200 Linux regression tracking (Thorsten > Leemhuis) wrote: >>> I don't seem to have the permissions on BZ, but I'm guessing we could >>> do the opposite - you could flip bugbot on first to have it flush the BZ >>> report to the list, and then reply on the list with regzbot tracking? >> >> That's the plan for the future, but for now I don't want to do that, as >> it might mess up other peoples workflows, as hinted above already and >> discussed here: >> >> https://lore.kernel.org/all/1f0ebf13-ab0f-d512-6106-3ebf7cb372f1@leemhuis.info/ >> >> That was only recently, but if you jump in there as well it might >> persuade Konstantin to enable bugbot for other products/components. Then >> I could and would do what you suggested. > > CC: workflows > > I'm a bit confused. I understand that we don't want to automatically > send all bugzilla reports to the ML. But AFAIU this is to avoid spamming > the list / messing with people's existing BZ workflow. > If you pre-triage the problem and decide to forward it to the list - > whether you do it with buzbot + regzbot or manual + regzbot is moot. > > The bugbot can be enabled per BZ entry (AFAIU), so you can flip it > individually for the thread you want to report. It should flush that > BZ to the list. At which point you can follow your normal ML regression > process. > > Where did I go off the rails? You missed that Konstantin (now CCed) is just a bit careful for the bugbot bring up and therefore for now only allows bugbot to be enabled for BZ entries that are filed against the product/component combination Linux/Kernel. I could reassigning bugs there, but that would break the workflow for maintainers like Kalle, which look at all bugs assigned to their product/component combo (Drivers/network-wireless in Kalle's case). Ciao, Thorsten ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [regression] Kernel OOPS on boot with Kernel 6.3(.1) and RTL8153 Gigabit Ethernet Adapter 2023-05-11 13:25 ` Thorsten Leemhuis @ 2023-05-11 16:06 ` Konstantin Ryabitsev 0 siblings, 0 replies; 3+ messages in thread From: Konstantin Ryabitsev @ 2023-05-11 16:06 UTC (permalink / raw) To: Thorsten Leemhuis Cc: Jakub Kicinski, Linux regressions mailing list, Bjørn Mork, Hayes Wang, netdev, Paolo Abeni, Eric Dumazet, David S. Miller, Stanislav Fomichev, workflows On Thu, May 11, 2023 at 03:25:47PM +0200, Thorsten Leemhuis wrote: > > The bugbot can be enabled per BZ entry (AFAIU), so you can flip it > > individually for the thread you want to report. It should flush that > > BZ to the list. At which point you can follow your normal ML regression > > process. > > > > Where did I go off the rails? > > You missed that Konstantin (now CCed) is just a bit careful for the > bugbot bring up and therefore for now only allows bugbot to be enabled > for BZ entries that are filed against the product/component combination > Linux/Kernel. I could reassigning bugs there, but that would break the > workflow for maintainers like Kalle, which look at all bugs assigned to > their product/component combo (Drivers/network-wireless in Kalle's case). I hope to start opening this up to other products within the next few weeks, as things are looking fairly stable for our initial tests. -K ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-05-11 16:06 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <ec4be122-e213-ca5b-f5d6-e8f9c3fd3bee@leemhuis.info>
[not found] ` <87lei36q27.fsf@miraculix.mork.no>
[not found] ` <20230505120436.6ff8cfca@kernel.org>
[not found] ` <57dbce31-daa9-9674-513e-f123b94950da@leemhuis.info>
[not found] ` <20230505123744.16666106@kernel.org>
[not found] ` <9284a9ec-d7c9-68e8-7384-07291894937b@leemhuis.info>
2023-05-08 20:09 ` [regression] Kernel OOPS on boot with Kernel 6.3(.1) and RTL8153 Gigabit Ethernet Adapter Jakub Kicinski
2023-05-11 13:25 ` Thorsten Leemhuis
2023-05-11 16:06 ` Konstantin Ryabitsev
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox