glusterfs.git/run-tests.sh, branch v4.1.1

run-tests.sh: added dependency check for netstat

2018-03-12T22:19:24+00:00

Because bug-924726.t depends on netstat, tests failed before. This got resolved
by adding respective check to run-tests.sh.

Enabled respective test again.

Change-Id: I70c9bff03379ed9ee8cd95842c3501dfb50b8e86
BUG: 1312830
Signed-off-by: Sven Fischer

tests: bring option of per test timeout

2018-02-15T08:20:19+00:00

This uses 'timeout' command with 300 seconds default. Right now,
there is just 1 test which takes more than that in a properly
setup machine.

Ideally best case is set the default to something like 30 seconds,
and if a test is supposed to take more than that, owner should add
a timeout line to test knowingly. That way, it makes test writers
think about a time limit too.

Change-Id: I747005ce1f208aeb2ecbf899e8feea487ecd21a0
Signed-off-by: Amar Tumballi

tests: merge stdout and stderr output

2018-01-30T05:59:09+00:00

Add -m argument to 'prove' command-line.

Fix xxhsum.c debugging output to keep 'prove' happy.

Change-Id: I03485d5f5e43ae4ce454a275ec98bc18384ed00c
Signed-off-by: Milind Changire

Revert "run-tests.sh: provide retry count option"

2017-12-06T14:47:00+00:00

This change was actually causing failures to be reported as passing.

This reverts commit 4e798113229eab68e9e02364bb094a4ab8274c65.

Change-Id: I02b06e7f2af03419d922de8ad7e6948ae8cb8d06

run-tests.sh: provide retry count option

2017-12-05T14:22:52+00:00

and default it to 5.

With this change, if any test fails due to timing issues (because of
slower/faster VM etc), there is a retry logic which gets triggered.
Many times, if a test successfully fails more than 5 times, there may
be a genuine issue with it, one should take a serious look at the
failing test.

Change-Id: Ia88e3293fd2724b0f9f09d8bc026560792fc1578
BUG: 1517961
Signed-off-by: Amar Tumballi

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