Re: [Gluster-infra] [Gluster-devel] Weekly Untriaged Bugs

[Atin Mukherjee]

While I understand this report captured bugs filed since last 1 week and do
not have ‘Triaged’ keyword, does it make better sense to exclude bugs which
aren’t in NEW state?

I believe the intention of this report is to check what all bugs haven’t
been looked at by maintainers/developers yet. BZs which are already fixed
or in ASSIGNED/POST state need not to feature in this list is what I
believe as otherwise it gives a false impression that too many bugs are
getting unnoticed which isn’t the reality. Thoughts?

On Mon, 22 Apr 2019 at 07:15,  wrote:

> [...truncated 6 lines...]
> https://bugzilla.redhat.com/1699023 / core: Brick is not able to detach
> successfully in brick_mux environment
> https://bugzilla.redhat.com/1695416 / core: client log flooding with
> intentional socket shutdown message when a brick is down
> https://bugzilla.redhat.com/1695480 / core: Global Thread Pool
> https://bugzilla.redhat.com/1694943 / core: parallel-readdir slows down
> directory listing
> https://bugzilla.redhat.com/1700295 / core: The data couldn't be flushed
> immediately even with O_SYNC in glfs_create or with
> glfs_fsync/glfs_fdatasync after glfs_write.
> https://bugzilla.redhat.com/1698861 / disperse: Renaming a directory when
> 2 bricks of multiple disperse subvols are down leaves both old and new dirs
> on the bricks.
> https://bugzilla.redhat.com/1697293 / distribute: DHT: print hash and
> layout values in hexadecimal format in the logs
> https://bugzilla.redhat.com/1701039 / distribute: gluster replica 3
> arbiter Unfortunately data not distributed equally
> https://bugzilla.redhat.com/1697971 / fuse: Segfault in FUSE process,
> potential use after free
> https://bugzilla.redhat.com/1694139 / glusterd: Error waiting for job
> 'heketi-storage-copy-job' to complete on one-node k3s deployment.
> https://bugzilla.redhat.com/1695099 / glusterd: The number of glusterfs
> processes keeps increasing, using all available resources
> https://bugzilla.redhat.com/1692349 / project-infrastructure:
> gluster-csi-containers job is failing
> https://bugzilla.redhat.com/1698716 / project-infrastructure: Regression
> job did not vote for https://review.gluster.org/#/c/glusterfs/+/22366/
> https://bugzilla.redhat.com/1698694 / project-infrastructure: regression
> job isn't voting back to gerrit
> https://bugzilla.redhat.com/1699712 / project-infrastructure: regression
> job is voting Success even in case of failure
> https://bugzilla.redhat.com/1693385 / project-infrastructure: request to
> change the version of fedora in fedora-smoke-job
> https://bugzilla.redhat.com/1695484 / project-infrastructure: smoke fails
> with "Build root is locked by another process"
> https://bugzilla.redhat.com/1693184 / replicate: A brick
> process(glusterfsd) died with 'memory violation'
> https://bugzilla.redhat.com/1698566 / selfheal: shd crashed while
> executing ./tests/bugs/core/bug-1432542-mpx-restart-crash.t in CI
> https://bugzilla.redhat.com/1699309 / snapshot: Gluster snapshot fails
> with systemd autmounted bricks
> https://bugzilla.redhat.com/1696633 / tests: GlusterFs v4.1.5 Tests from
> /tests/bugs/ module failing on Intel
> https://bugzilla.redhat.com/1697812 / website: mention a pointer to all
> the mailing lists available under glusterfs project(
> https://www.gluster.org/community/)
> [...truncated 2 lines...]___
> Gluster-devel mailing list
> gluster-de...@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-devel

-- 
- Atin (atinm)
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Weekly Untriaged Bugs

[Niels de Vos]

On Mon, Oct 01, 2018 at 07:37:13AM +0530, Sankarshan Mukhopadhyay wrote:
> On Mon, Oct 1, 2018 at 7:15 AM  wrote:
> >
> 
> 
> > https://bugzilla.redhat.com/1625501 / project-infrastructure: gd2 smoke 
> > tests fail with cannot create directory ‘/var/lib/glusterd’: Permission 
> > denied
> > https://bugzilla.redhat.com/1626453 / project-infrastructure: 
> > glusterd2-containers nightly job failing
> > https://bugzilla.redhat.com/1627624 / project-infrastructure: Run gd2-smoke 
> > only after smoke passes
> > https://bugzilla.redhat.com/1631390 / project-infrastructure: Run smoke and 
> > regression on a patch only after passing clang-format job
> > https://bugzilla.redhat.com/1633497 / project-infrastructure: Unable to 
> > subscribe to upstream mailing list.
> 
> Some of these have on-going commentary but are in NEW, perhaps they
> should be in ASSIGNED.

Or add Triaged to the list of Keywords in the BZs.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Weekly Untriaged Bugs

[Michael Scherer]

Le lundi 01 octobre 2018 à 07:37 +0530, Sankarshan Mukhopadhyay a
écrit :
> On Mon, Oct 1, 2018 at 7:15 AM  wrote:
> > 
> 
> 
> > https://bugzilla.redhat.com/1625501 / project-infrastructure: gd2
> > smoke tests fail with cannot create directory ‘/var/lib/glusterd’:
> > Permission denied
> > https://bugzilla.redhat.com/1626453 / project-infrastructure:
> > glusterd2-containers nightly job failing
> > https://bugzilla.redhat.com/1627624 / project-infrastructure: Run
> > gd2-smoke only after smoke passes
> > https://bugzilla.redhat.com/1631390 / project-infrastructure: Run
> > smoke and regression on a patch only after passing clang-format job
> > https://bugzilla.redhat.com/1633497 / project-infrastructure:
> > Unable to subscribe to upstream mailing list.
> 
> Some of these have on-going commentary but are in NEW, perhaps they
> should be in ASSIGNED.

Since we are not participating in the usual bug triage process (afaik),
I think the right solution should rather to exclude infra bugs from the
list/check. 

This is not the first problem we have due to the sharing of product
field in bugzilla, it also happen when bugs get closed, etc :/ 

-- 
Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS



signature.asc
Description: This is a digitally signed message part
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Weekly Untriaged Bugs

[Sankarshan Mukhopadhyay]

On Mon, Oct 1, 2018 at 7:15 AM  wrote:
>


> https://bugzilla.redhat.com/1625501 / project-infrastructure: gd2 smoke tests 
> fail with cannot create directory ‘/var/lib/glusterd’: Permission denied
> https://bugzilla.redhat.com/1626453 / project-infrastructure: 
> glusterd2-containers nightly job failing
> https://bugzilla.redhat.com/1627624 / project-infrastructure: Run gd2-smoke 
> only after smoke passes
> https://bugzilla.redhat.com/1631390 / project-infrastructure: Run smoke and 
> regression on a patch only after passing clang-format job
> https://bugzilla.redhat.com/1633497 / project-infrastructure: Unable to 
> subscribe to upstream mailing list.

Some of these have on-going commentary but are in NEW, perhaps they
should be in ASSIGNED.

-- 
sankarshan mukhopadhyay

___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Weekly Untriaged Bugs

[Deepshikha Khandelwal]

On Mon, Jul 9, 2018 at 7:37 AM, Sankarshan Mukhopadhyay
 wrote:
> On Mon, Jul 9, 2018 at 7:15 AM,   wrote:
>
>> https://bugzilla.redhat.com/1591276 / project-infrastructure: Automated way 
>> to run coverity runs on project every week.
>> https://bugzilla.redhat.com/1592736 / project-infrastructure: gerrit-stage 
>> SSL cert expired
>> https://bugzilla.redhat.com/1597543 / project-infrastructure: Install 
>> python3 on all the internal machines.
>> https://bugzilla.redhat.com/1594857 / project-infrastructure: Make smoke 
>> runs detect test cases added to patch
>> https://bugzilla.redhat.com/1597731 / project-infrastructure: need 
>> 'shellcheck' in smoke.
>> https://bugzilla.redhat.com/1593414 / project-infrastructure: Retire/close 
>> 3.10 and 4.0 gerrit dashboard
>> https://bugzilla.redhat.com/1598326 / project-infrastructure: Setup CI for 
>> gluster-block
>
> At this point, is not Bhumika setting it up for the (sub) project? Or,
> is this a tracker to federate it?
>
Yes, Bhumika is setting it up. It's just to keep the track.
>> https://bugzilla.redhat.com/1597351 / project-infrastructure: Smoke should 
>> fail on commits against closed github issues
>> https://bugzilla.redhat.com/1598328 / project-infrastructure: Unable to 
>> subscribe to automated-testing mailing list
>
> At least this last one seems to have active conversations, is it
> expected to be in NEW?
>
> --
> sankarshan mukhopadhyay
> 
> ___
> Gluster-infra mailing list
> Gluster-infra@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-infra
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra

Re: [Gluster-infra] [Gluster-devel] Weekly Untriaged Bugs

[Sankarshan Mukhopadhyay]

On Mon, Jul 9, 2018 at 7:15 AM,   wrote:

> https://bugzilla.redhat.com/1591276 / project-infrastructure: Automated way 
> to run coverity runs on project every week.
> https://bugzilla.redhat.com/1592736 / project-infrastructure: gerrit-stage 
> SSL cert expired
> https://bugzilla.redhat.com/1597543 / project-infrastructure: Install python3 
> on all the internal machines.
> https://bugzilla.redhat.com/1594857 / project-infrastructure: Make smoke runs 
> detect test cases added to patch
> https://bugzilla.redhat.com/1597731 / project-infrastructure: need 
> 'shellcheck' in smoke.
> https://bugzilla.redhat.com/1593414 / project-infrastructure: Retire/close 
> 3.10 and 4.0 gerrit dashboard
> https://bugzilla.redhat.com/1598326 / project-infrastructure: Setup CI for 
> gluster-block

At this point, is not Bhumika setting it up for the (sub) project? Or,
is this a tracker to federate it?

> https://bugzilla.redhat.com/1597351 / project-infrastructure: Smoke should 
> fail on commits against closed github issues
> https://bugzilla.redhat.com/1598328 / project-infrastructure: Unable to 
> subscribe to automated-testing mailing list

At least this last one seems to have active conversations, is it
expected to be in NEW?

-- 
sankarshan mukhopadhyay

___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra