[Gluster-Maintainers] Build failed in Jenkins: netbsd-periodic #167

2017-08-12 Thread jenkins 
See 

--
[...truncated 362.49 KB...]
ok 12, LINENUM:44
ok 13, LINENUM:45
ok 14, LINENUM:49
ok 15, LINENUM:52
ok 16, LINENUM:53
ok 17, LINENUM:57
ok 18, LINENUM:58
ok 19, LINENUM:59
ok 20, LINENUM:60
ok 21, LINENUM:61
ok 22, LINENUM:62
ok 23, LINENUM:63
ok 24, LINENUM:65
ok 25, LINENUM:66
ok 26, LINENUM:67
ok 27, LINENUM:68
ok 28, LINENUM:69
ok 29, LINENUM:70
ok 30, LINENUM:71
ok 31, LINENUM:72
ok 32, LINENUM:73
ok 33, LINENUM:75
ok 34, LINENUM:76
ok 35, LINENUM:78
ok 36, LINENUM:82
ok 37, LINENUM:83
ok 38, LINENUM:88
ok 39, LINENUM:93
ok
All tests successful.
Files=1, Tests=39, 44 wallclock secs ( 0.05 usr  0.00 sys +  2.88 cusr  3.99 
csys =  6.92 CPU)
Result: PASS
End of test ./tests/bitrot/bug-1294786.t




[01:40:50] Running tests in file ./tests/bitrot/bug-1373520.t
getfattr: Removing leading '/' from absolute path names
./tests/bitrot/bug-1373520.t .. 
1..26
ok 1, LINENUM:8
ok 2, LINENUM:9
ok 3, LINENUM:12
ok 4, LINENUM:13
ok 5, LINENUM:14
ok 6, LINENUM:17
ok 7, LINENUM:20
ok 8, LINENUM:21
ok 9, LINENUM:24
ok 10, LINENUM:25
ok 11, LINENUM:28
ok 12, LINENUM:30
ok 13, LINENUM:33
ok 14, LINENUM:39
ok 15, LINENUM:40
ok 16, LINENUM:41
ok 17, LINENUM:42
ok 18, LINENUM:44
ok 19, LINENUM:45
ok 20, LINENUM:46
ok 21, LINENUM:47
ok 22, LINENUM:50
ok 23, LINENUM:53
not ok 24 Got "0" instead of "512", LINENUM:54
FAILED COMMAND: 512 path_size /d/backends/patchy5/FILE1
ok 25, LINENUM:55
not ok 26 Got "0" instead of "512", LINENUM:56
FAILED COMMAND: 512 path_size /d/backends/patchy5/HL_FILE1
Failed 2/26 subtests 

Test Summary Report
---
./tests/bitrot/bug-1373520.t (Wstat: 0 Tests: 26 Failed: 2)
  Failed tests:  24, 26
Files=1, Tests=26, 195 wallclock secs ( 0.04 usr -0.01 sys +  9.41 cusr 13.34 
csys = 22.78 CPU)
Result: FAIL
./tests/bitrot/bug-1373520.t: bad status 1

   *
   *   REGRESSION FAILED   *
   * Retrying failed tests in case *
   * we got some spurious failures *
   *

getfattr: Removing leading '/' from absolute path names
./tests/bitrot/bug-1373520.t .. 
1..26
ok 1, LINENUM:8
ok 2, LINENUM:9
ok 3, LINENUM:12
ok 4, LINENUM:13
ok 5, LINENUM:14
ok 6, LINENUM:17
ok 7, LINENUM:20
ok 8, LINENUM:21
ok 9, LINENUM:24
ok 10, LINENUM:25
ok 11, LINENUM:28
ok 12, LINENUM:30
ok 13, LINENUM:33
ok 14, LINENUM:39
ok 15, LINENUM:40
ok 16, LINENUM:41
ok 17, LINENUM:42
ok 18, LINENUM:44
ok 19, LINENUM:45
ok 20, LINENUM:46
ok 21, LINENUM:47
ok 22, LINENUM:50
ok 23, LINENUM:53
not ok 24 Got "0" instead of "512", LINENUM:54
FAILED COMMAND: 512 path_size /d/backends/patchy5/FILE1
ok 25, LINENUM:55
not ok 26 Got "0" instead of "512", LINENUM:56
FAILED COMMAND: 512 path_size /d/backends/patchy5/HL_FILE1
Failed 2/26 subtests 

Test Summary Report
---
./tests/bitrot/bug-1373520.t (Wstat: 0 Tests: 26 Failed: 2)
  Failed tests:  24, 26
Files=1, Tests=26, 194 wallclock secs ( 0.04 usr  0.00 sys +  9.30 cusr 13.27 
csys = 22.61 CPU)
Result: FAIL
End of test ./tests/bitrot/bug-1373520.t



Run complete

Number of tests found: 131
Number of tests selected for run based on pattern: 131
Number of tests skipped as they were marked bad:   16
Number of tests skipped because of known_issues:   16
Number of tests that were run: 99

Tests ordered by time taken, slowest to fastest: 

./tests/basic/distribute/rebal-all-nodes-migrate.t  -  338 second
./tests/basic/afr/lk-quorum.t  -  264 second
./tests/basic/afr/split-brain-favorite-child-policy.t  -  256 second
./tests/bitrot/bug-1373520.t  -  195 second
./tests/basic/afr/gfid-mismatch-resolution-with-fav-child-policy.t  -  168 
second
./tests/basic/afr/self-heald.t  -  150 second
./tests/basic/afr/self-heal.t  -  150 second
./tests/basic/afr/sparse-file-self-heal.t  -  147 second
./tests/basic/afr/gfid-mismatch-resolution-with-cli.t  -  123 second
./tests/basic/afr/entry-self-heal.t  -  103 second
./tests/basic/afr/split-brain-heal-info.t  -  91 second
./tests/basic/afr/metadata-self-heal.t  -  68 second
./tests/basic/afr/quorum.t  -  66 second
./tests/basic/afr/inodelk.t  -  65 second
./tests/basic/stats-dump.t  -  63 second
./tests/basic/mount-nfs-auth.t  -  61 second
./tests/basic/afr/split-brain-healing.t  -  58 second
./tests/basic/afr/arbiter-add-brick.t  -  55 second
./tests/basic/afr/arbiter.t  -  53 second
./tests/basic/geo-replication/marker-xattrs.t  -  46 second
./tests/bitrot/bug-1294786.t  -  44 second

Re: [Gluster-Maintainers] [Gluster-devel] Proposed Protocol changes for 4.0: Need feedback.

2017-08-12 Thread Prashanth Pai 
Hi Niels,

I guess these are the related issues you were looking for:
https://github.com/gluster/glusterfs/issues/203
https://github.com/gluster/glusterfs/issues/67

On Fri, Aug 11, 2017 at 6:41 PM, Niels de Vos  wrote:

> On Fri, Aug 11, 2017 at 06:04:36PM +0530, Amar Tumballi wrote:
> > Hi All,
> >
> > Below are the proposed protocol changes (ie, XDR changes on the wire) we
> > are thinking for Gluster 4.0.
>
> One of the things that is missing in this list, is to have dictionary
> entries have a (key, type, value) format. This makes it possible to have
> all the values XDR encoded/decoded correctly. When new values get
> transported over the network, we can force the need for XDR encoding
> functions for these types.
>
> I thought there was a GitHub issue for this already (or maybe a bug?),
> but I fail to find it.
>
> Niels
> ___
> Gluster-devel mailing list
> gluster-de...@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>
___
maintainers mailing list
maintainers@gluster.org
http://lists.gluster.org/mailman/listinfo/maintainers

[Gluster-Maintainers] Build failed in Jenkins: netbsd-periodic #166

2017-08-12 Thread jenkins 
See 

--
[...truncated 361.98 KB...]
ok 12, LINENUM:44
ok 13, LINENUM:45
ok 14, LINENUM:49
ok 15, LINENUM:52
ok 16, LINENUM:53
ok 17, LINENUM:57
ok 18, LINENUM:58
ok 19, LINENUM:59
ok 20, LINENUM:60
ok 21, LINENUM:61
ok 22, LINENUM:62
ok 23, LINENUM:63
ok 24, LINENUM:65
ok 25, LINENUM:66
ok 26, LINENUM:67
ok 27, LINENUM:68
ok 28, LINENUM:69
ok 29, LINENUM:70
ok 30, LINENUM:71
ok 31, LINENUM:72
ok 32, LINENUM:73
ok 33, LINENUM:75
ok 34, LINENUM:76
ok 35, LINENUM:78
ok 36, LINENUM:82
ok 37, LINENUM:83
ok 38, LINENUM:88
ok 39, LINENUM:93
ok
All tests successful.
Files=1, Tests=39, 45 wallclock secs ( 0.04 usr  0.00 sys +  2.96 cusr  3.94 
csys =  6.94 CPU)
Result: PASS
End of test ./tests/bitrot/bug-1294786.t




[17:40:13] Running tests in file ./tests/bitrot/bug-1373520.t
getfattr: Removing leading '/' from absolute path names
./tests/bitrot/bug-1373520.t .. 
1..26
ok 1, LINENUM:8
ok 2, LINENUM:9
ok 3, LINENUM:12
ok 4, LINENUM:13
ok 5, LINENUM:14
ok 6, LINENUM:17
ok 7, LINENUM:20
ok 8, LINENUM:21
ok 9, LINENUM:24
ok 10, LINENUM:25
ok 11, LINENUM:28
ok 12, LINENUM:30
ok 13, LINENUM:33
ok 14, LINENUM:39
ok 15, LINENUM:40
ok 16, LINENUM:41
ok 17, LINENUM:42
ok 18, LINENUM:44
ok 19, LINENUM:45
ok 20, LINENUM:46
ok 21, LINENUM:47
ok 22, LINENUM:50
ok 23, LINENUM:53
not ok 24 Got "0" instead of "512", LINENUM:54
FAILED COMMAND: 512 path_size /d/backends/patchy5/FILE1
ok 25, LINENUM:55
not ok 26 Got "0" instead of "512", LINENUM:56
FAILED COMMAND: 512 path_size /d/backends/patchy5/HL_FILE1
Failed 2/26 subtests 

Test Summary Report
---
./tests/bitrot/bug-1373520.t (Wstat: 0 Tests: 26 Failed: 2)
  Failed tests:  24, 26
Files=1, Tests=26, 196 wallclock secs ( 0.03 usr  0.01 sys +  9.33 cusr 13.35 
csys = 22.72 CPU)
Result: FAIL
./tests/bitrot/bug-1373520.t: bad status 1

   *
   *   REGRESSION FAILED   *
   * Retrying failed tests in case *
   * we got some spurious failures *
   *

getfattr: Removing leading '/' from absolute path names
./tests/bitrot/bug-1373520.t .. 
1..26
ok 1, LINENUM:8
ok 2, LINENUM:9
ok 3, LINENUM:12
ok 4, LINENUM:13
ok 5, LINENUM:14
ok 6, LINENUM:17
ok 7, LINENUM:20
ok 8, LINENUM:21
ok 9, LINENUM:24
ok 10, LINENUM:25
ok 11, LINENUM:28
ok 12, LINENUM:30
ok 13, LINENUM:33
ok 14, LINENUM:39
ok 15, LINENUM:40
ok 16, LINENUM:41
ok 17, LINENUM:42
ok 18, LINENUM:44
ok 19, LINENUM:45
ok 20, LINENUM:46
ok 21, LINENUM:47
ok 22, LINENUM:50
ok 23, LINENUM:53
not ok 24 Got "0" instead of "512", LINENUM:54
FAILED COMMAND: 512 path_size /d/backends/patchy5/FILE1
ok 25, LINENUM:55
not ok 26 Got "0" instead of "512", LINENUM:56
FAILED COMMAND: 512 path_size /d/backends/patchy5/HL_FILE1
Failed 2/26 subtests 

Test Summary Report
---
./tests/bitrot/bug-1373520.t (Wstat: 0 Tests: 26 Failed: 2)
  Failed tests:  24, 26
Files=1, Tests=26, 195 wallclock secs ( 0.03 usr  0.01 sys +  9.35 cusr 13.54 
csys = 22.93 CPU)
Result: FAIL
End of test ./tests/bitrot/bug-1373520.t



Run complete

Number of tests found: 131
Number of tests selected for run based on pattern: 131
Number of tests skipped as they were marked bad:   16
Number of tests skipped because of known_issues:   16
Number of tests that were run: 99

Tests ordered by time taken, slowest to fastest: 

./tests/basic/distribute/rebal-all-nodes-migrate.t  -  328 second
./tests/basic/afr/lk-quorum.t  -  268 second
./tests/basic/afr/split-brain-favorite-child-policy.t  -  254 second
./tests/bitrot/bug-1373520.t  -  196 second
./tests/basic/afr/gfid-mismatch-resolution-with-fav-child-policy.t  -  161 
second
./tests/basic/afr/self-heal.t  -  148 second
./tests/basic/afr/self-heald.t  -  136 second
./tests/basic/afr/sparse-file-self-heal.t  -  134 second
./tests/basic/afr/gfid-mismatch-resolution-with-cli.t  -  116 second
./tests/basic/afr/entry-self-heal.t  -  108 second
./tests/basic/afr/split-brain-heal-info.t  -  92 second
./tests/basic/afr/quorum.t  -  69 second
./tests/basic/afr/metadata-self-heal.t  -  68 second
./tests/basic/afr/inodelk.t  -  65 second
./tests/basic/mount-nfs-auth.t  -  62 second
./tests/basic/afr/split-brain-healing.t  -  58 second
./tests/basic/afr/arbiter.t  -  52 second
./tests/basic/afr/arbiter-add-brick.t  -  51 second
./tests/basic/afr/gfid-self-heal.t  -  47 second
./tests/basic/geo-replication/marker-xattrs.t  -  47 second
./tests/bitrot/bug-1294786.t  -  45 second

Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-3.10.5 released

2017-08-12 Thread Niels de Vos 
On Sat, Aug 12, 2017 at 12:49:14PM +, Gluster Build System wrote:
> 
> 
> SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.10.5.tar.gz
> 
> This release is made off v3.10.5

Packages for the CentOS Storage SIG are available for testing. Please
let me know when someone tried them (even minor checks are sufficient)
so that I can mark them for releasing to the CentOS mirrors.

  # yum install centos-release-gluster310
  # yum --enablerepo=centos-gluster310-test install \
  glusterfs-server-3.10.5-1.el7


I never received any feedback for the 3.10.4 packages, and have now
tagged them for release (fingers crossed!). Once the CentOS team does a
new sync run, the 3.10.4 packages will be available on the mirrors.

Thanks,
Niels
___
maintainers mailing list
maintainers@gluster.org
http://lists.gluster.org/mailman/listinfo/maintainers

[Gluster-Maintainers] glusterfs-3.10.5 released

2017-08-12 Thread Gluster Build System 


SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.10.5.tar.gz

This release is made off v3.10.5

-- Gluster Build System
___
maintainers mailing list
maintainers@gluster.org
http://lists.gluster.org/mailman/listinfo/maintainers

[Gluster-Maintainers] Jenkins build is back to normal : netbsd-periodic #165

2017-08-12 Thread jenkins 
See 

___
maintainers mailing list
maintainers@gluster.org
http://lists.gluster.org/mailman/listinfo/maintainers