[Gluster-devel] Fwd: [Ci-users] Maintenance Window 22-Aug-2018 12:00PM UTC

2018-08-20 Thread Nigel Babu 
Heads up: Centos CI will be undergoing maintenance tomorrow.

-- Forwarded message -
From: Brian Stinson 
Date: Tue, Aug 21, 2018 at 1:58 AM
Subject: [Ci-users] Maintenance Window 22-Aug-2018 12:00PM UTC
To: 



Hi All,

Due to some pending OS updates we will be rebooting machines in the
CentOS CI Infrastructure starting at 12:00 Noon UTC on Wednesday
22-Aug-2018

We expect this to take up to 2 hours as we reboot various machines in
the CI Infrastructure. During this period we'll hold the master Jenkins
queue for resubmission after we complete this window.

Let us know here or in #centos-devel on Freenode if you have any
questions or comments.

Cheers!

--
Brian Stinson
CentOS CI Infrastructure Team
___
Ci-users mailing list
ci-us...@centos.org
https://lists.centos.org/mailman/listinfo/ci-users


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

[Gluster-devel] Test health report (week ending 19th Aug. 2018)

2018-08-20 Thread Shyam Ranganathan 
Although tests have stabilized quite a bit, and from the maintainers
meeting we know that some tests have patches coming in, here is a
readout of other tests that needed a retry. We need to reduce failures
on retries as well, to be able to not have spurious or other failures in
test runs.

Tests being worked on (from the maintainers meeting notes):
- bug-1586020-mark-dirty-for-entry-txn-on-quorum-failure.t

Other retries and failures, request component maintainers to look at the
test case and resulting failures and post back any findings to the lists
to take things forward,

https://build.gluster.org/job/line-coverage/481/console
20:10:01 1 test(s) needed retry
20:10:01 ./tests/basic/distribute/rebal-all-nodes-migrate.t

https://build.gluster.org/job/line-coverage/483/console
18:42:01 2 test(s) needed retry
18:42:01 ./tests/basic/tier/fops-during-migration-pause.t
18:42:01
./tests/bugs/replicate/bug-1586020-mark-dirty-for-entry-txn-on-quorum-failure.t
(fix in progress)

https://build.gluster.org/job/regression-test-burn-in/4067/console
18:27:21 1 test(s) generated core
18:27:21 ./tests/bugs/readdir-ahead/bug-1436090.t

https://build.gluster.org/job/regression-test-with-multiplex/828/console
18:19:39 1 test(s) needed retry
18:19:39 ./tests/bugs/glusterd/validating-server-quorum.t

https://build.gluster.org/job/regression-test-with-multiplex/829/console
18:24:14 2 test(s) needed retry
18:24:14 ./tests/00-geo-rep/georep-basic-dr-rsync.t
18:24:14 ./tests/bugs/glusterd/quorum-validation.t

https://build.gluster.org/job/regression-test-with-multiplex/831/console
18:20:49 1 test(s) generated core
18:20:49 ./tests/basic/ec/ec-5-2.t

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

[Gluster-devel] Maintainer meeting minutes: 20th August, 2018

2018-08-20 Thread Amar Tumballi 
BJ Link

   - Bridge: https://bluejeans.com/217609845
   - Download: https://bluejeans.com/s/IVExy

Attendance

   - Nithya, Amar, Nigel, Sunny, Ravi, Kaleb, kshlm, Raghavendra M,
   Raghavendra G, Shyam (Partial)
   - Calendar Declines: ppai

Agenda

   -

   Master lockdown, and other stability initiatives
   - Where do we stand?
 - [Amar] Everything looks good at this point. Not as many random
 failures as there used to be.
  - What needs further attention?
 - There are still some random failures on brick-mux regression.
  - Any metrics?
 - [Atin]
 
https://fstat.gluster.org/summary?start_date=2018-08-13&end_date=2018-08-20
  - tracks the failures reported since master lock down is revoked.
 - [Atin] Overall, things look much more stable after a bunch of
 test fixes being worked on during this lock down.
 - c7 nightly had reported green 5 out of 7 times, 1 failed with
 some core (
 
https://lists.gluster.org/pipermail/gluster-devel/2018-August/055298.html),
 18th August’s run seem to hit n/w failure.
 - brick mux nightly had seen couple of issues since last week, 1.
 crash from tests/basic/ec/ec-5-2.t & 2. spurious failure from
 
tests/bugs/replicate/bug-1586020-mark-dirty-for-entry-txn-on-quorum-failure.t.
 (fix merged today)
 - line-cov nightly had failed once in
 
tests/bugs/replicate/bug-1586020-mark-dirty-for-entry-txn-on-quorum-failure.t
 (fix merged today)
  -

   Outstanding review queue is quite long, need review attention.
   - Maintainers keep track of their lanes and how many patches are pending.
   -

   v5.0 branching
   - Can we get all the features completed by today??
 - What are the features we’re targetting for this release? Github
 doesn’t give a clear picture. This is a problem.
  - Will this release be just a stability release?
 - There is nothing wrong in calling it a stability release.
 - If there are no features, and as we are still working on
 coverity, clang and other code coverage initiatives, should
we delay the
 branching?
 - If we’re calling this a stability release, perhaps we should
 look into memory leaks that have been reported on the lists already.
  - What about clang-formatter? Planned email content here
  
 - Around branching point is the time to get this done.
 - The messaging around “personal preference” for style vs “project
 preference” needs to be clear.
 - [Nigel] Still need to see the content, and give the proper set
 of tasks.
 - 2 options:
-
   1. Big change where we can change all files, and make
   currently posted patches conflict.
-
   1. Or make user change the file he touches with clang format.
- Precommit hook Vs Server side change.
 - problem with git review, or git push directly compared to
 `./rfc.sh`. We need a smoke job for sure.
 - Should we force everyone to install clang? Make it optional for
 user.
 - AI on Amar for giving a date for this activity completion, by
 EOD 21st August, 2018.
  - [Kaleb] what is the status of python3? (fedora 29(?) and rhel8 are
  looming.)
 - Seemingly, we’re not 100% python3 ready
 
.
 There are bugs that need fixing.
 - Ship with Python3 and we’ll fix the bugs as we find them.
 - Let’s change all the shebangs to python3.
  -

   GCS:
   - Any updates?
 - CSI driver under review -
 https://github.com/gluster/gluster-csi-driver/pull/11
- We can land the patch and fix the license later too.
- Good to go ahead and merge, and then get the followup
patches, it would move things faster.
- Kaushal to review Madhu’s changes on top of the PR, and if
things look OK, then we can merge the PR.
 - GD2 + Gluster nightly container image -
 https://hub.docker.com/r/gluster/glusterd2-nightly/
-

https://github.com/gluster/glusterd2/tree/master/extras/nightly-container
 - Build pipeline - in progress. Waiting on infra to have all the
 deps installed.
 - Deployment script in-progress
  -

   Mountpoint
   - Presentations ready?
  - All set for travel?
 - Some delays with Visa arrival, few maintainers who were supposed
 to travel from India will be confirming only by end of the week.
  -

   Round Table
   - [Amar] Can we disable bd (block-device) translator from the
  build/code? N

[Gluster-devel] Coverity covscan for 2018-08-20-21199aae (master branch)

2018-08-20 Thread staticanalysis 


GlusterFS Coverity covscan results for the master branch are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-08-20-21199aae/

Coverity covscan results for other active branches are also available at
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/

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