glusterfs.git/run-tests.sh, branch v3.10.7

explicitly specify executor to be bash for tests

2017-04-24T15:32:14+00:00

We use prove command to run tests. Sometimes tests fail rather strangely
with error as shown below:

Not a perl script at ./tests/bugs/core/bug-1111557.t line 1.
./tests/bugs/core/bug-1111557.t ..
Dubious, test returned 25 (wstat 6400, 0x1900)
No subtests run

https://build.gluster.org/job/centos6-regression/3818/consoleFull
https://build.gluster.org/job/centos6-regression/3819/consoleFull
https://build.gluster.org/job/centos6-regression/3801/consoleFull

Quote from man page

``
 "--exec"
       Normally you can just pass a list of Perl tests and the harness
will know how to execute them.  However, if your tests are not written in Perl
or if you want all tests invoked exactly the same way, use the "-e",
or "--exec" switch:

        prove --exec '/usr/bin/ruby -w' t/
```

Hence, better to comply with recommended practice although it might not
be the reason for this failure.

> BUG: 1438858
> Signed-off-by: Raghavendra Talur 
> Reviewed-on: https://review.gluster.org/16996
> Smoke: Gluster Build System 
> Reviewed-by: N Balachandran 
> NetBSD-regression: NetBSD Build System 
> Reviewed-by: Nigel Babu 
> CentOS-regression: Gluster Build System 
> Reviewed-by: Jeff Darcy 
(cherry picked from commit d6b88e9b8b02813620c3c1a2ea49d58d29062b3e)

Change-Id: If7a0baf20698f8497ef3e8fc422fa67063a4651f
BUG: 1444773
Signed-off-by: Raghavendra Talur 
Reviewed-on: https://review.gluster.org/17103
Tested-by: N Balachandran 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

core: run many bricks within one glusterfsd process

2017-02-02T00:54:58+00:00

This patch adds support for multiple brick translator stacks running in
a single brick server process.  This reduces our per-brick memory usage
by approximately 3x, and our appetite for TCP ports even more.  It also
creates potential to avoid process/thread thrashing, and to improve QoS
by scheduling more carefully across the bricks, but realizing that
potential will require further work.

Multiplexing is controlled by the "cluster.brick-multiplex" global
option.  By default it's off, and bricks are started in separate
processes as before.  If multiplexing is enabled, then *compatible*
bricks (mostly those with the same transport options) will be started in
the same process.

Backport of:
> Change-Id: I45059454e51d6f4cbb29a4953359c09a408695cb
> BUG: 1385758
> Reviewed-on: https://review.gluster.org/14763

Change-Id: I4bce9080f6c93d50171823298fdf920258317ee8
BUG: 1418091
Signed-off-by: Jeff Darcy 
Reviewed-on: https://review.gluster.org/16496
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Shyamsundar Ranganathan

tests: fix per-test core detection

2016-04-07T11:29:42+00:00

Commit 9933c5ab in glusterfs-patch-acceptance-tests broke the code here
to count cores after each test, with two bad effects:

 * Tests continue to run after the job is already guaranteed to fail,
   tying up resources and delaying jobs for other patches.

 * Cores aren't detected until the end of the job, long after it might
   have been possible to figure out what was going on at the time the
   process died.

The current check here works for the current code in the other repo, but
could break if the two repos are changed without coordination again.

Change-Id: Ica9222c3474fddf8e3b40074da2bdfd4dabb79d7
Signed-off-by: Jeff Darcy 
Reviewed-on: http://review.gluster.org/13921
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System

tests: return correct value from run_head_tests when no tests are found

2016-03-12T12:59:37+00:00

Also added a diff filter to avoid listing deleted tests.  Thanks to
Raghavendra Talur for the suggestion.

Change-Id: Ied2d552d227b55027211c07db6ee5dc20979596b
Signed-off-by: Jeff Darcy 
Reviewed-on: https://review.gluster.org/13686
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Tested-by: Gluster Build System

tests: run tests from the most recent commit first

2016-03-11T15:21:09+00:00

Change-Id: If11f552543bf0f1f0e9756e9f2237b72e44b7aed
Signed-off-by: Jeff Darcy 
Reviewed-on: http://review.gluster.org/13439
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Raghavendra Talur

tests: Add mechanism for disabled tests

2016-03-10T07:19:40+00:00

Requirements:
Should be able to skip tests from run-tests.sh run.
Should be granular enough to disable on subset of OSes.

Solution:
Tests can have special comment lines with some comma separated values
within them.

Key names used to determine test status are
G_TESTDEF_TEST_STATUS_CENTOS6
G_TESTDEF_TEST_STATUS_NETBSD7
Some examples:
G_TESTDEF_TEST_STATUS_CENTOS6=BAD_TEST,BUG=123456
G_TESTDEF_TEST_STATUS_NETBSD7=KNOWN_ISSUE,BUG=4444444
G_TESTDEF_TEST_STATUS_CENTOS6=BAD_TEST,BUG=123456;555555
You can change status of test to enabled or delete the line only if all the
bugs are closed or modified or if the patch fixes it.

Change-Id: Idee21fecaa5837fd4bd06e613f5c07a024f7b0c2
BUG: 1295704
Signed-off-by: Raghavendra Talur 
Reviewed-on: http://review.gluster.org/13393
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Rajesh Joseph 
Reviewed-by: Kaushal M

tests: Move tier-file-create.t to bad tests

2016-03-08T20:00:39+00:00

Change-Id: Iaddb244699b0e2647a67a75f257e4c47e0e69e0d
BUG: 1315560
Signed-off-by: Krutika Dhananjay 
Reviewed-on: http://review.gluster.org/13632
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Dan Lambright 
Reviewed-by: Jeff Darcy

Remove replace-brick-self-heal.t from bad-tests

2016-03-04T12:44:34+00:00

Unable to recreate any failures even after running
the test for more than an hour in a loop.

Change-Id: Id1c7e60d39bce6b312dbb4ea0975079348bb1649
BUG: 1314549
Signed-off-by: Anuradha Talur 
Reviewed-on: http://review.gluster.org/13599
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Pranith Kumar Karampuri

cli/tests: disable tiering on NetBSD

2016-03-02T02:34:01+00:00

As proposed in the following email:

  http://www.gluster.org/pipermail/gluster-devel/2016-February/048464.html

Short version: tiering tests on NetBSD are failing often enough to
impede other development, and also to cast doubt on whether tiering even
works on that platform.  The most effective way to satisfy both
developers' and users' interests is to disable tiering on NetBSD until
such time as someone becomes available to resolve these problems another
way.

Change-Id: I7375527c339e2650a7e8e900a0d0572013213544
Signed-off-by: Jeff Darcy 
Reviewed-on: http://review.gluster.org/13535
Smoke: Gluster Build System 
Reviewed-by: Joseph Fernandes
CentOS-regression: Gluster Build System 
NetBSD-regression: NetBSD Build System

Mark slowest tests in regression test output

2016-02-15T17:27:04+00:00

Recording of elapsed time is only accurate to the second. This should
be okay. Some *BSD systems may not have '%N' support in date command.

Change-Id: I81e887c4783b052317922f3a4af37ec3676fb67d
Signed-off-by: Prashanth Pai 
Reviewed-on: http://review.gluster.org/13430
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Raghavendra Talur