<div dir="ltr"><div>This list also captures the BZs which are in NEW state. The search description goes like this:</div><div><ul class="gmail-search_description"><li>
<strong>Status:</strong>
NEW
</li><li>
<strong>Product:</strong>
GlusterFS
</li><li>
<strong>Changed:</strong>
(is greater than or equal to)
-4w
</li><li>
<strong>Creation date:</strong>
(changed after)
-4w
</li><li>
<strong>Keywords:</strong>
(does not contain the string)
Triaged
</li></ul> </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Apr 28, 2019 at 6:44 PM Atin Mukherjee <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div dir="auto">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?</div><div dir="auto"><br></div><div dir="auto">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?</div></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, 22 Apr 2019 at 07:15, <<a href="mailto:jenkins@build.gluster.org" target="_blank">jenkins@build.gluster.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">[...truncated 6 lines...]<br>
<a href="https://bugzilla.redhat.com/1699023" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1699023</a> / core: Brick is not able to detach successfully in brick_mux environment<br>
<a href="https://bugzilla.redhat.com/1695416" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1695416</a> / core: client log flooding with intentional socket shutdown message when a brick is down<br>
<a href="https://bugzilla.redhat.com/1695480" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1695480</a> / core: Global Thread Pool<br>
<a href="https://bugzilla.redhat.com/1694943" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1694943</a> / core: parallel-readdir slows down directory listing<br>
<a href="https://bugzilla.redhat.com/1700295" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1700295</a> / core: The data couldn't be flushed immediately even with O_SYNC in glfs_create or with glfs_fsync/glfs_fdatasync after glfs_write.<br>
<a href="https://bugzilla.redhat.com/1698861" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1698861</a> / disperse: Renaming a directory when 2 bricks of multiple disperse subvols are down leaves both old and new dirs on the bricks.<br>
<a href="https://bugzilla.redhat.com/1697293" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1697293</a> / distribute: DHT: print hash and layout values in hexadecimal format in the logs<br>
<a href="https://bugzilla.redhat.com/1701039" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1701039</a> / distribute: gluster replica 3 arbiter Unfortunately data not distributed equally<br>
<a href="https://bugzilla.redhat.com/1697971" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1697971</a> / fuse: Segfault in FUSE process, potential use after free<br>
<a href="https://bugzilla.redhat.com/1694139" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1694139</a> / glusterd: Error waiting for job 'heketi-storage-copy-job' to complete on one-node k3s deployment.<br>
<a href="https://bugzilla.redhat.com/1695099" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1695099</a> / glusterd: The number of glusterfs processes keeps increasing, using all available resources<br>
<a href="https://bugzilla.redhat.com/1692349" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1692349</a> / project-infrastructure: gluster-csi-containers job is failing<br>
<a href="https://bugzilla.redhat.com/1698716" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1698716</a> / project-infrastructure: Regression job did not vote for <a href="https://review.gluster.org/#/c/glusterfs/+/22366/" rel="noreferrer" target="_blank">https://review.gluster.org/#/c/glusterfs/+/22366/</a><br>
<a href="https://bugzilla.redhat.com/1698694" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1698694</a> / project-infrastructure: regression job isn't voting back to gerrit<br>
<a href="https://bugzilla.redhat.com/1699712" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1699712</a> / project-infrastructure: regression job is voting Success even in case of failure<br>
<a href="https://bugzilla.redhat.com/1693385" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1693385</a> / project-infrastructure: request to change the version of fedora in fedora-smoke-job<br>
<a href="https://bugzilla.redhat.com/1695484" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1695484</a> / project-infrastructure: smoke fails with "Build root is locked by another process"<br>
<a href="https://bugzilla.redhat.com/1693184" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1693184</a> / replicate: A brick process(glusterfsd) died with 'memory violation'<br>
<a href="https://bugzilla.redhat.com/1698566" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1698566</a> / selfheal: shd crashed while executing ./tests/bugs/core/bug-1432542-mpx-restart-crash.t in CI<br>
<a href="https://bugzilla.redhat.com/1699309" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1699309</a> / snapshot: Gluster snapshot fails with systemd autmounted bricks<br>
<a href="https://bugzilla.redhat.com/1696633" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1696633</a> / tests: GlusterFs v4.1.5 Tests from /tests/bugs/ module failing on Intel<br>
<a href="https://bugzilla.redhat.com/1697812" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/1697812</a> / website: mention a pointer to all the mailing lists available under glusterfs project(<a href="https://www.gluster.org/community/" rel="noreferrer" target="_blank">https://www.gluster.org/community/</a>)<br>
[...truncated 2 lines...]_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a></blockquote></div></div>-- <br><div dir="ltr" class="gmail-m_1391567758250870654gmail_signature">- Atin (atinm)</div>
_______________________________________________<br>
Gluster-infra mailing list<br>
<a href="mailto:Gluster-infra@gluster.org" target="_blank">Gluster-infra@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-infra" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-infra</a></blockquote></div>