* Bugzilla Component for KUnit? @ 2019-10-02 21:53 ` Brendan Higgins 2019-10-04 18:55 ` [Kernel.org Helpdesk #80110] " Konstantin Ryabitsev via RT 0 siblings, 1 reply; 9+ messages in thread From: Brendan Higgins @ 2019-10-02 21:53 UTC (permalink / raw) To: helpdesk; +Cc: kunit-dev, linux-kselftest Hi, I am thinking about requesting a Bugzilla component for my kernel project KUnit. I am not sure if this is the right place for it. Some background on KUnit: We are working on adding unit testing for the Linux kernel[1][2]. We have our initial patchset that introduces the subsystem in the process of being merged (Linus sent our PR back to us for a minor fix[3], so it should be in either 5.4-rc2 or 5.5, but is nevertheless in linux-next). However, we also have a staging repo that people are using and some supporting code that lives outside of the kernel. So I am trying to figure out: 1. Is it appropriate to request a Bugzilla component before our subsystem has been merged into torvalds/master? I would just wait, but I have some users looking to file issues, so I would prefer to provide them something sooner rather than later. 2. Is it appropriate to use the kernel's Bugzilla to track issues outside of the Linux kernel? As I mention above, we have code that lives outside of the kernel; is it appropriate to use kernel.org's Bugzilla for this? 3. Does Bugzilla match my planned usage model? It doesn't look like Bugzilla get's much usage aside from reporting bugs. I want to use it for tracking feature progress and things like that. Is that okay? If kernel.org's Bugzilla is not a fit for what I want to do, that's fine. I just want to make sure before I go off and potentially fracture a central bug repository by creating my own somewhere else. Thanks! [1] https://lwn.net/Articles/780985/ [2] https://google.github.io/kunit-docs/third_party/kernel/docs/index.html [3] https://lore.kernel.org/lkml/be8059f4-8e8f-cd18-0978-a9c861f6396b@linuxfoundation.org/ ^ permalink raw reply [flat|nested] 9+ messages in thread
* [Kernel.org Helpdesk #80110] Bugzilla Component for KUnit? 2019-10-02 21:53 ` Bugzilla Component for KUnit? Brendan Higgins @ 2019-10-04 18:55 ` Konstantin Ryabitsev via RT 2019-10-07 21:21 ` Brendan Higgins 0 siblings, 1 reply; 9+ messages in thread From: Konstantin Ryabitsev via RT @ 2019-10-04 18:55 UTC (permalink / raw) To: brendanhiggins; +Cc: kunit-dev, linux-kselftest On 2019-10-02 17:53:58, brendanhiggins@google.com wrote: > Hi, > > I am thinking about requesting a Bugzilla component for my kernel > project KUnit. I am not sure if this is the right place for it. Some > background on KUnit: We are working on adding unit testing for the > Linux > kernel[1][2]. We have our initial patchset that introduces the > subsystem > in the process of being merged (Linus sent our PR back to us for a > minor > fix[3], so it should be in either 5.4-rc2 or 5.5, but is nevertheless > in > linux-next). However, we also have a staging repo that people are > using > and some supporting code that lives outside of the kernel. > > So I am trying to figure out: > > 1. Is it appropriate to request a Bugzilla component before our > subsystem has been merged into torvalds/master? I would just wait, > but I have some users looking to file issues, so I would prefer to > provide them something sooner rather than later. > > 2. Is it appropriate to use the kernel's Bugzilla to track issues > outside of the Linux kernel? As I mention above, we have code that > lives outside of the kernel; is it appropriate to use kernel.org's > Bugzilla for this? > > 3. Does Bugzilla match my planned usage model? It doesn't look like > Bugzilla get's much usage aside from reporting bugs. I want to use > it for tracking feature progress and things like that. Is that > okay? Yes, we can certainly host this on bugzilla.kernel.org. Would you be okay with Tools/KUnit as product/category? Regards, -- Konstantin Ryabitsev Director, LF Projects IT The Linux Foundation ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Kernel.org Helpdesk #80110] Bugzilla Component for KUnit? 2019-10-04 18:55 ` [Kernel.org Helpdesk #80110] " Konstantin Ryabitsev via RT @ 2019-10-07 21:21 ` Brendan Higgins 2019-10-07 21:21 ` brendanhiggins@google.com via RT [not found] ` <rt-4.4.0-14627-1570483310-1693.80110-6-0@linuxfoundation> 0 siblings, 2 replies; 9+ messages in thread From: Brendan Higgins @ 2019-10-07 21:21 UTC (permalink / raw) To: kernel-helpdesk; +Cc: kunit-dev, open list:KERNEL SELFTEST FRAMEWORK On Fri, Oct 4, 2019 at 11:55 AM Konstantin Ryabitsev via RT <kernel-helpdesk@rt.linuxfoundation.org> wrote: > > On 2019-10-02 17:53:58, brendanhiggins@google.com wrote: > > Hi, > > > > I am thinking about requesting a Bugzilla component for my kernel > > project KUnit. I am not sure if this is the right place for it. Some > > background on KUnit: We are working on adding unit testing for the > > Linux > > kernel[1][2]. We have our initial patchset that introduces the > > subsystem > > in the process of being merged (Linus sent our PR back to us for a > > minor > > fix[3], so it should be in either 5.4-rc2 or 5.5, but is nevertheless > > in > > linux-next). However, we also have a staging repo that people are > > using > > and some supporting code that lives outside of the kernel. > > > > So I am trying to figure out: > > > > 1. Is it appropriate to request a Bugzilla component before our > > subsystem has been merged into torvalds/master? I would just wait, > > but I have some users looking to file issues, so I would prefer to > > provide them something sooner rather than later. > > > > 2. Is it appropriate to use the kernel's Bugzilla to track issues > > outside of the Linux kernel? As I mention above, we have code that > > lives outside of the kernel; is it appropriate to use kernel.org's > > Bugzilla for this? > > > > 3. Does Bugzilla match my planned usage model? It doesn't look like > > Bugzilla get's much usage aside from reporting bugs. I want to use > > it for tracking feature progress and things like that. Is that > > okay? > > Yes, we can certainly host this on bugzilla.kernel.org. Would you be okay with Tools/KUnit as product/category? Cool, well as long as none of my above points are an issue for you. Then yes, can you create me a component? I am fine with Tools/KUnit as the product/category. Thanks! ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Kernel.org Helpdesk #80110] Bugzilla Component for KUnit? 2019-10-07 21:21 ` Brendan Higgins @ 2019-10-07 21:21 ` brendanhiggins@google.com via RT 2019-10-15 2:41 ` Brendan Higgins [not found] ` <rt-4.4.0-14627-1570483310-1693.80110-6-0@linuxfoundation> 1 sibling, 1 reply; 9+ messages in thread From: brendanhiggins@google.com via RT @ 2019-10-07 21:21 UTC (permalink / raw) Cc: kunit-dev, linux-kselftest On Fri, Oct 4, 2019 at 11:55 AM Konstantin Ryabitsev via RT <kernel-helpdesk@rt.linuxfoundation.org> wrote: > > On 2019-10-02 17:53:58, brendanhiggins@google.com wrote: > > Hi, > > > > I am thinking about requesting a Bugzilla component for my kernel > > project KUnit. I am not sure if this is the right place for it. Some > > background on KUnit: We are working on adding unit testing for the > > Linux > > kernel[1][2]. We have our initial patchset that introduces the > > subsystem > > in the process of being merged (Linus sent our PR back to us for a > > minor > > fix[3], so it should be in either 5.4-rc2 or 5.5, but is nevertheless > > in > > linux-next). However, we also have a staging repo that people are > > using > > and some supporting code that lives outside of the kernel. > > > > So I am trying to figure out: > > > > 1. Is it appropriate to request a Bugzilla component before our > > subsystem has been merged into torvalds/master? I would just wait, > > but I have some users looking to file issues, so I would prefer to > > provide them something sooner rather than later. > > > > 2. Is it appropriate to use the kernel's Bugzilla to track issues > > outside of the Linux kernel? As I mention above, we have code that > > lives outside of the kernel; is it appropriate to use kernel.org's > > Bugzilla for this? > > > > 3. Does Bugzilla match my planned usage model? It doesn't look like > > Bugzilla get's much usage aside from reporting bugs. I want to use > > it for tracking feature progress and things like that. Is that > > okay? > > Yes, we can certainly host this on bugzilla.kernel.org. Would you be okay with Tools/KUnit as product/category? Cool, well as long as none of my above points are an issue for you. Then yes, can you create me a component? I am fine with Tools/KUnit as the product/category. Thanks! ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Kernel.org Helpdesk #80110] Bugzilla Component for KUnit? 2019-10-07 21:21 ` brendanhiggins@google.com via RT @ 2019-10-15 2:41 ` Brendan Higgins 2019-10-15 2:42 ` brendanhiggins@google.com via RT 0 siblings, 1 reply; 9+ messages in thread From: Brendan Higgins @ 2019-10-15 2:41 UTC (permalink / raw) To: kernel-helpdesk; +Cc: KUnit Development, open list:KERNEL SELFTEST FRAMEWORK On Mon, Oct 7, 2019 at 2:21 PM brendanhiggins@google.com via RT <kernel-helpdesk@rt.linuxfoundation.org> wrote: > > On Fri, Oct 4, 2019 at 11:55 AM Konstantin Ryabitsev via RT > <kernel-helpdesk@rt.linuxfoundation.org> wrote: > > > > On 2019-10-02 17:53:58, brendanhiggins@google.com wrote: > > > Hi, > > > > > > I am thinking about requesting a Bugzilla component for my kernel > > > project KUnit. I am not sure if this is the right place for it. Some > > > background on KUnit: We are working on adding unit testing for the > > > Linux > > > kernel[1][2]. We have our initial patchset that introduces the > > > subsystem > > > in the process of being merged (Linus sent our PR back to us for a > > > minor > > > fix[3], so it should be in either 5.4-rc2 or 5.5, but is nevertheless > > > in > > > linux-next). However, we also have a staging repo that people are > > > using > > > and some supporting code that lives outside of the kernel. > > > > > > So I am trying to figure out: > > > > > > 1. Is it appropriate to request a Bugzilla component before our > > > subsystem has been merged into torvalds/master? I would just wait, > > > but I have some users looking to file issues, so I would prefer to > > > provide them something sooner rather than later. > > > > > > 2. Is it appropriate to use the kernel's Bugzilla to track issues > > > outside of the Linux kernel? As I mention above, we have code that > > > lives outside of the kernel; is it appropriate to use kernel.org's > > > Bugzilla for this? > > > > > > 3. Does Bugzilla match my planned usage model? It doesn't look like > > > Bugzilla get's much usage aside from reporting bugs. I want to use > > > it for tracking feature progress and things like that. Is that > > > okay? > > > > Yes, we can certainly host this on bugzilla.kernel.org. Would you be okay with Tools/KUnit as product/category? > > Cool, well as long as none of my above points are an issue for you. > Then yes, can you create me a component? I am fine with Tools/KUnit as > the product/category. Ping. ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Kernel.org Helpdesk #80110] Bugzilla Component for KUnit? 2019-10-15 2:41 ` Brendan Higgins @ 2019-10-15 2:42 ` brendanhiggins@google.com via RT 0 siblings, 0 replies; 9+ messages in thread From: brendanhiggins@google.com via RT @ 2019-10-15 2:42 UTC (permalink / raw) Cc: kunit-dev, linux-kselftest On Mon, Oct 7, 2019 at 2:21 PM brendanhiggins@google.com via RT <kernel-helpdesk@rt.linuxfoundation.org> wrote: > > On Fri, Oct 4, 2019 at 11:55 AM Konstantin Ryabitsev via RT > <kernel-helpdesk@rt.linuxfoundation.org> wrote: > > > > On 2019-10-02 17:53:58, brendanhiggins@google.com wrote: > > > Hi, > > > > > > I am thinking about requesting a Bugzilla component for my kernel > > > project KUnit. I am not sure if this is the right place for it. Some > > > background on KUnit: We are working on adding unit testing for the > > > Linux > > > kernel[1][2]. We have our initial patchset that introduces the > > > subsystem > > > in the process of being merged (Linus sent our PR back to us for a > > > minor > > > fix[3], so it should be in either 5.4-rc2 or 5.5, but is nevertheless > > > in > > > linux-next). However, we also have a staging repo that people are > > > using > > > and some supporting code that lives outside of the kernel. > > > > > > So I am trying to figure out: > > > > > > 1. Is it appropriate to request a Bugzilla component before our > > > subsystem has been merged into torvalds/master? I would just wait, > > > but I have some users looking to file issues, so I would prefer to > > > provide them something sooner rather than later. > > > > > > 2. Is it appropriate to use the kernel's Bugzilla to track issues > > > outside of the Linux kernel? As I mention above, we have code that > > > lives outside of the kernel; is it appropriate to use kernel.org's > > > Bugzilla for this? > > > > > > 3. Does Bugzilla match my planned usage model? It doesn't look like > > > Bugzilla get's much usage aside from reporting bugs. I want to use > > > it for tracking feature progress and things like that. Is that > > > okay? > > > > Yes, we can certainly host this on bugzilla.kernel.org. Would you be okay with Tools/KUnit as product/category? > > Cool, well as long as none of my above points are an issue for you. > Then yes, can you create me a component? I am fine with Tools/KUnit as > the product/category. Ping. ^ permalink raw reply [flat|nested] 9+ messages in thread
[parent not found: <rt-4.4.0-14627-1570483310-1693.80110-6-0@linuxfoundation>]
* [Kernel.org Helpdesk #80110] Bugzilla Component for KUnit? [not found] ` <rt-4.4.0-14627-1570483310-1693.80110-6-0@linuxfoundation> @ 2019-10-15 20:14 ` Konstantin Ryabitsev via RT 2019-10-16 21:05 ` Brendan Higgins 0 siblings, 1 reply; 9+ messages in thread From: Konstantin Ryabitsev via RT @ 2019-10-15 20:14 UTC (permalink / raw) To: brendanhiggins; +Cc: kunit-dev, linux-kselftest On 2019-10-07 17:21:50, brendanhiggins@google.com wrote: > On Fri, Oct 4, 2019 at 11:55 AM Konstantin Ryabitsev via RT > <kernel-helpdesk@rt.linuxfoundation.org> wrote: > > > > On 2019-10-02 17:53:58, brendanhiggins@google.com wrote: > > > Hi, > > > > > > I am thinking about requesting a Bugzilla component for my kernel > > > project KUnit. I am not sure if this is the right place for it. > > > Some > > > background on KUnit: We are working on adding unit testing for the > > > Linux > > > kernel[1][2]. We have our initial patchset that introduces the > > > subsystem > > > in the process of being merged (Linus sent our PR back to us for a > > > minor > > > fix[3], so it should be in either 5.4-rc2 or 5.5, but is > > > nevertheless > > > in > > > linux-next). However, we also have a staging repo that people are > > > using > > > and some supporting code that lives outside of the kernel. > > > > > > So I am trying to figure out: > > > > > > 1. Is it appropriate to request a Bugzilla component before our > > > subsystem has been merged into torvalds/master? I would just > > > wait, > > > but I have some users looking to file issues, so I would prefer > > > to > > > provide them something sooner rather than later. > > > > > > 2. Is it appropriate to use the kernel's Bugzilla to track issues > > > outside of the Linux kernel? As I mention above, we have code > > > that > > > lives outside of the kernel; is it appropriate to use > > > kernel.org's > > > Bugzilla for this? > > > > > > 3. Does Bugzilla match my planned usage model? It doesn't look like > > > Bugzilla get's much usage aside from reporting bugs. I want to > > > use > > > it for tracking feature progress and things like that. Is that > > > okay? > > > > Yes, we can certainly host this on bugzilla.kernel.org. Would you be > > okay with Tools/KUnit as product/category? > > Cool, well as long as none of my above points are an issue for you. > Then yes, can you create me a component? I am fine with Tools/KUnit as > the product/category. Apologies for the delay, mostly due to Thanksgiving in Canada. You should be able to start using Tools/KUnit now. It uses a default virtual assignee tools_kunit@kernel-bugs.kernel.org, so to start receiving bugmail for it, please follow instructions on this page: https://korg.wiki.kernel.org/userdoc/bugzilla#to_start_getting_bug_reports_for_a_component Best regards, -- Konstantin Ryabitsev Director, LF Projects IT The Linux Foundation ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Kernel.org Helpdesk #80110] Bugzilla Component for KUnit? 2019-10-15 20:14 ` Konstantin Ryabitsev via RT @ 2019-10-16 21:05 ` Brendan Higgins 2019-10-16 21:05 ` brendanhiggins@google.com via RT 0 siblings, 1 reply; 9+ messages in thread From: Brendan Higgins @ 2019-10-16 21:05 UTC (permalink / raw) To: kernel-helpdesk; +Cc: KUnit Development, open list:KERNEL SELFTEST FRAMEWORK On Tue, Oct 15, 2019 at 1:14 PM Konstantin Ryabitsev via RT <kernel-helpdesk@rt.linuxfoundation.org> wrote: > > On 2019-10-07 17:21:50, brendanhiggins@google.com wrote: > > On Fri, Oct 4, 2019 at 11:55 AM Konstantin Ryabitsev via RT > > <kernel-helpdesk@rt.linuxfoundation.org> wrote: > > > > > > On 2019-10-02 17:53:58, brendanhiggins@google.com wrote: > > > > Hi, > > > > > > > > I am thinking about requesting a Bugzilla component for my kernel > > > > project KUnit. I am not sure if this is the right place for it. > > > > Some > > > > background on KUnit: We are working on adding unit testing for the > > > > Linux > > > > kernel[1][2]. We have our initial patchset that introduces the > > > > subsystem > > > > in the process of being merged (Linus sent our PR back to us for a > > > > minor > > > > fix[3], so it should be in either 5.4-rc2 or 5.5, but is > > > > nevertheless > > > > in > > > > linux-next). However, we also have a staging repo that people are > > > > using > > > > and some supporting code that lives outside of the kernel. > > > > > > > > So I am trying to figure out: > > > > > > > > 1. Is it appropriate to request a Bugzilla component before our > > > > subsystem has been merged into torvalds/master? I would just > > > > wait, > > > > but I have some users looking to file issues, so I would prefer > > > > to > > > > provide them something sooner rather than later. > > > > > > > > 2. Is it appropriate to use the kernel's Bugzilla to track issues > > > > outside of the Linux kernel? As I mention above, we have code > > > > that > > > > lives outside of the kernel; is it appropriate to use > > > > kernel.org's > > > > Bugzilla for this? > > > > > > > > 3. Does Bugzilla match my planned usage model? It doesn't look like > > > > Bugzilla get's much usage aside from reporting bugs. I want to > > > > use > > > > it for tracking feature progress and things like that. Is that > > > > okay? > > > > > > Yes, we can certainly host this on bugzilla.kernel.org. Would you be > > > okay with Tools/KUnit as product/category? > > > > Cool, well as long as none of my above points are an issue for you. > > Then yes, can you create me a component? I am fine with Tools/KUnit as > > the product/category. > > Apologies for the delay, mostly due to Thanksgiving in Canada. You should be able to start using Tools/KUnit now. It uses a default virtual assignee tools_kunit@kernel-bugs.kernel.org, so to start receiving bugmail for it, please follow instructions on this page: No worries. > > https://korg.wiki.kernel.org/userdoc/bugzilla#to_start_getting_bug_reports_for_a_component Thanks! ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Kernel.org Helpdesk #80110] Bugzilla Component for KUnit? 2019-10-16 21:05 ` Brendan Higgins @ 2019-10-16 21:05 ` brendanhiggins@google.com via RT 0 siblings, 0 replies; 9+ messages in thread From: brendanhiggins@google.com via RT @ 2019-10-16 21:05 UTC (permalink / raw) Cc: kunit-dev, linux-kselftest On Tue, Oct 15, 2019 at 1:14 PM Konstantin Ryabitsev via RT <kernel-helpdesk@rt.linuxfoundation.org> wrote: > > On 2019-10-07 17:21:50, brendanhiggins@google.com wrote: > > On Fri, Oct 4, 2019 at 11:55 AM Konstantin Ryabitsev via RT > > <kernel-helpdesk@rt.linuxfoundation.org> wrote: > > > > > > On 2019-10-02 17:53:58, brendanhiggins@google.com wrote: > > > > Hi, > > > > > > > > I am thinking about requesting a Bugzilla component for my kernel > > > > project KUnit. I am not sure if this is the right place for it. > > > > Some > > > > background on KUnit: We are working on adding unit testing for the > > > > Linux > > > > kernel[1][2]. We have our initial patchset that introduces the > > > > subsystem > > > > in the process of being merged (Linus sent our PR back to us for a > > > > minor > > > > fix[3], so it should be in either 5.4-rc2 or 5.5, but is > > > > nevertheless > > > > in > > > > linux-next). However, we also have a staging repo that people are > > > > using > > > > and some supporting code that lives outside of the kernel. > > > > > > > > So I am trying to figure out: > > > > > > > > 1. Is it appropriate to request a Bugzilla component before our > > > > subsystem has been merged into torvalds/master? I would just > > > > wait, > > > > but I have some users looking to file issues, so I would prefer > > > > to > > > > provide them something sooner rather than later. > > > > > > > > 2. Is it appropriate to use the kernel's Bugzilla to track issues > > > > outside of the Linux kernel? As I mention above, we have code > > > > that > > > > lives outside of the kernel; is it appropriate to use > > > > kernel.org's > > > > Bugzilla for this? > > > > > > > > 3. Does Bugzilla match my planned usage model? It doesn't look like > > > > Bugzilla get's much usage aside from reporting bugs. I want to > > > > use > > > > it for tracking feature progress and things like that. Is that > > > > okay? > > > > > > Yes, we can certainly host this on bugzilla.kernel.org. Would you be > > > okay with Tools/KUnit as product/category? > > > > Cool, well as long as none of my above points are an issue for you. > > Then yes, can you create me a component? I am fine with Tools/KUnit as > > the product/category. > > Apologies for the delay, mostly due to Thanksgiving in Canada. You should be able to start using Tools/KUnit now. It uses a default virtual assignee tools_kunit@kernel-bugs.kernel.org, so to start receiving bugmail for it, please follow instructions on this page: No worries. > > https://korg.wiki.kernel.org/userdoc/bugzilla#to_start_getting_bug_reports_for_a_component Thanks! ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2019-10-16 21:06 UTC | newest] Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- [not found] <RT-Ticket-80110@linuxfoundation> 2019-10-02 21:53 ` Bugzilla Component for KUnit? Brendan Higgins 2019-10-04 18:55 ` [Kernel.org Helpdesk #80110] " Konstantin Ryabitsev via RT 2019-10-07 21:21 ` Brendan Higgins 2019-10-07 21:21 ` brendanhiggins@google.com via RT 2019-10-15 2:41 ` Brendan Higgins 2019-10-15 2:42 ` brendanhiggins@google.com via RT [not found] ` <rt-4.4.0-14627-1570483310-1693.80110-6-0@linuxfoundation> 2019-10-15 20:14 ` Konstantin Ryabitsev via RT 2019-10-16 21:05 ` Brendan Higgins 2019-10-16 21:05 ` brendanhiggins@google.com via RT
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).