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

run-tests.sh: log failed tests at the end

2017-07-21T12:38:40+00:00

Two benefits:

1. People who subscribe to emails on regression failures
   (like maintainers@gluster.org), can see the list of failed tests
   in the email itself, instead of clicking on the link and checking
   for failures.

2. When we visit the regression console, instead of scrolling to the
   exact position to see which tests failed, we can just press 'End'
   and would be able to check failures.

Change-Id: Ibb4ac9575c5d32bae9c40c31fb53c9488b94421a
Signed-off-by: Amar Tumballi 
Reviewed-on: https://review.gluster.org/17843
Smoke: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Reviewed-by: Niels de Vos 
Reviewed-by: Jeff Darcy 
CentOS-regression: Gluster Build System

tests: fix typo

2017-04-30T21:45:49+00:00

I've been staring at this for ages, and it finally got to me.

Change-Id: I472dc2b2cf3ab175014ed673d73b543aa3e14d14
Signed-off-by: Jeff Darcy 
Reviewed-on: https://review.gluster.org/17140
Tested-by: Jeff Darcy 
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
Reviewed-by: Zhou Zhengping 
CentOS-regression: Gluster Build System 
Reviewed-by: Amar Tumballi

explicitly specify executor to be bash for tests

2017-04-05T13:09:41+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.

Change-Id: If7a0baf20698f8497ef3e8fc422fa67063a4651f
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

core: run many bricks within one glusterfsd process

2017-01-31T00:13: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.

Change-Id: I45059454e51d6f4cbb29a4953359c09a408695cb
BUG: 1385758
Signed-off-by: Jeff Darcy 
Reviewed-on: https://review.gluster.org/14763
Smoke: Gluster Build System 
NetBSD-regression: NetBSD Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Vijay Bellur

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