ebugs JIRAs

[Eric Badger <eb...@verizonmedia.com.INVALID>]

It seems as though ebugs is running a static code analyzer across all of
hadoop and creating a new JIRA for every issue it finds (15 JIRAs in the
past 3 hours). While this could potentially be useful, I don't think it's a
good idea at all to file a new JIRA for every single issue that is found.
It would be better to file 1 issue for every type of problem that it finds
or 1 issue per project (HDFS, YARN, etc.).

I have a feeling that we're going to either end up closing a bunch of these
as invalid or ignoring them all, so I figured we might as well talk about
this earlier rather than later.

Eric

Examples:
https://issues.apache.org/jira/browse/YARN-9534
https://issues.apache.org/jira/browse/HDFS-14467

Re: ebugs JIRAs

[Steve Loughran <st...@cloudera.com.INVALID>]

emailed the private@infra list asking for them to forward my email address
with the goal being to have a conversation about what is up.

for now, how about for each project people create an "ebugs exception
checker reports" and move everything underneath each one?

On Tue, May 7, 2019 at 9:52 AM Steve Loughran <st...@cloudera.com> wrote:

> does anyone have an email address of them.
>
> Some of the findings look valid, but a single summary would be the
> starting point, maybe with sub issues
>
> On Mon, May 6, 2019 at 5:41 PM Eric Badger
> <eb...@verizonmedia.com.invalid> wrote:
>
>> It seems as though ebugs is running a static code analyzer across all of
>> hadoop and creating a new JIRA for every issue it finds (15 JIRAs in the
>> past 3 hours). While this could potentially be useful, I don't think it's
>> a
>> good idea at all to file a new JIRA for every single issue that is found.
>> It would be better to file 1 issue for every type of problem that it finds
>> or 1 issue per project (HDFS, YARN, etc.).
>>
>> I have a feeling that we're going to either end up closing a bunch of
>> these
>> as invalid or ignoring them all, so I figured we might as well talk about
>> this earlier rather than later.
>>
>> Eric
>>
>> Examples:
>> https://issues.apache.org/jira/browse/YARN-9534
>> https://issues.apache.org/jira/browse/HDFS-14467
>>
>

Re: ebugs JIRAs

[Steve Loughran <st...@cloudera.com.INVALID>]

emailed the private@infra list asking for them to forward my email address
with the goal being to have a conversation about what is up.

for now, how about for each project people create an "ebugs exception
checker reports" and move everything underneath each one?

On Tue, May 7, 2019 at 9:52 AM Steve Loughran <st...@cloudera.com> wrote:

> does anyone have an email address of them.
>
> Some of the findings look valid, but a single summary would be the
> starting point, maybe with sub issues
>
> On Mon, May 6, 2019 at 5:41 PM Eric Badger
> <eb...@verizonmedia.com.invalid> wrote:
>
>> It seems as though ebugs is running a static code analyzer across all of
>> hadoop and creating a new JIRA for every issue it finds (15 JIRAs in the
>> past 3 hours). While this could potentially be useful, I don't think it's
>> a
>> good idea at all to file a new JIRA for every single issue that is found.
>> It would be better to file 1 issue for every type of problem that it finds
>> or 1 issue per project (HDFS, YARN, etc.).
>>
>> I have a feeling that we're going to either end up closing a bunch of
>> these
>> as invalid or ignoring them all, so I figured we might as well talk about
>> this earlier rather than later.
>>
>> Eric
>>
>> Examples:
>> https://issues.apache.org/jira/browse/YARN-9534
>> https://issues.apache.org/jira/browse/HDFS-14467
>>
>

Re: ebugs JIRAs

[Steve Loughran <st...@cloudera.com.INVALID>]

emailed the private@infra list asking for them to forward my email address
with the goal being to have a conversation about what is up.

for now, how about for each project people create an "ebugs exception
checker reports" and move everything underneath each one?

On Tue, May 7, 2019 at 9:52 AM Steve Loughran <st...@cloudera.com> wrote:

> does anyone have an email address of them.
>
> Some of the findings look valid, but a single summary would be the
> starting point, maybe with sub issues
>
> On Mon, May 6, 2019 at 5:41 PM Eric Badger
> <eb...@verizonmedia.com.invalid> wrote:
>
>> It seems as though ebugs is running a static code analyzer across all of
>> hadoop and creating a new JIRA for every issue it finds (15 JIRAs in the
>> past 3 hours). While this could potentially be useful, I don't think it's
>> a
>> good idea at all to file a new JIRA for every single issue that is found.
>> It would be better to file 1 issue for every type of problem that it finds
>> or 1 issue per project (HDFS, YARN, etc.).
>>
>> I have a feeling that we're going to either end up closing a bunch of
>> these
>> as invalid or ignoring them all, so I figured we might as well talk about
>> this earlier rather than later.
>>
>> Eric
>>
>> Examples:
>> https://issues.apache.org/jira/browse/YARN-9534
>> https://issues.apache.org/jira/browse/HDFS-14467
>>
>

Re: ebugs JIRAs

[Steve Loughran <st...@cloudera.com.INVALID>]

does anyone have an email address of them.

Some of the findings look valid, but a single summary would be the starting
point, maybe with sub issues

On Mon, May 6, 2019 at 5:41 PM Eric Badger <eb...@verizonmedia.com.invalid>
wrote:

> It seems as though ebugs is running a static code analyzer across all of
> hadoop and creating a new JIRA for every issue it finds (15 JIRAs in the
> past 3 hours). While this could potentially be useful, I don't think it's a
> good idea at all to file a new JIRA for every single issue that is found.
> It would be better to file 1 issue for every type of problem that it finds
> or 1 issue per project (HDFS, YARN, etc.).
>
> I have a feeling that we're going to either end up closing a bunch of these
> as invalid or ignoring them all, so I figured we might as well talk about
> this earlier rather than later.
>
> Eric
>
> Examples:
> https://issues.apache.org/jira/browse/YARN-9534
> https://issues.apache.org/jira/browse/HDFS-14467
>

Re: ebugs JIRAs

[Steve Loughran <st...@cloudera.com.INVALID>]

does anyone have an email address of them.

Some of the findings look valid, but a single summary would be the starting
point, maybe with sub issues

On Mon, May 6, 2019 at 5:41 PM Eric Badger <eb...@verizonmedia.com.invalid>
wrote:

> It seems as though ebugs is running a static code analyzer across all of
> hadoop and creating a new JIRA for every issue it finds (15 JIRAs in the
> past 3 hours). While this could potentially be useful, I don't think it's a
> good idea at all to file a new JIRA for every single issue that is found.
> It would be better to file 1 issue for every type of problem that it finds
> or 1 issue per project (HDFS, YARN, etc.).
>
> I have a feeling that we're going to either end up closing a bunch of these
> as invalid or ignoring them all, so I figured we might as well talk about
> this earlier rather than later.
>
> Eric
>
> Examples:
> https://issues.apache.org/jira/browse/YARN-9534
> https://issues.apache.org/jira/browse/HDFS-14467
>

Re: ebugs JIRAs

[Steve Loughran <st...@cloudera.com.INVALID>]

does anyone have an email address of them.

Some of the findings look valid, but a single summary would be the starting
point, maybe with sub issues

On Mon, May 6, 2019 at 5:41 PM Eric Badger <eb...@verizonmedia.com.invalid>
wrote:

> It seems as though ebugs is running a static code analyzer across all of
> hadoop and creating a new JIRA for every issue it finds (15 JIRAs in the
> past 3 hours). While this could potentially be useful, I don't think it's a
> good idea at all to file a new JIRA for every single issue that is found.
> It would be better to file 1 issue for every type of problem that it finds
> or 1 issue per project (HDFS, YARN, etc.).
>
> I have a feeling that we're going to either end up closing a bunch of these
> as invalid or ignoring them all, so I figured we might as well talk about
> this earlier rather than later.
>
> Eric
>
> Examples:
> https://issues.apache.org/jira/browse/YARN-9534
> https://issues.apache.org/jira/browse/HDFS-14467
>