On 2 August 2018 at 05:46, Shyam Ranganathan <srangana@xxxxxxxxxx> wrote:
Below is a summary of failures over the last 7 days on the nightly
health check jobs. This is one test per line, sorted in descending order
of occurrence (IOW, most frequent failure is on top).
The list includes spurious failures as well, IOW passed on a retry. This
is because if we do not weed out the spurious errors, failures may
persist and make it difficult to gauge the health of the branch.
The number at the end of the test line are Jenkins job numbers where
these failed. The job numbers runs as follows,
- https://build.gluster.org/job/regression-test-burn-in/ ID: 4048 - 4053
- https://build.gluster.org/job/line-coverage/ ID: 392 - 407
- https://build.gluster.org/job/regression-test-with- ID: 811multiplex/
- 817
So to get to job 4051 (say), use the link
https://build.gluster.org/job/regression-test-burn-in/4051
Atin has called out some folks for attention to some tests, consider
this a call out to others, if you see a test against your component,
help around root causing and fixing it is needed.
tests/bugs/core/bug-1432542-mpx-restart-crash.t, 4049, 4051, 4052, 405,
404, 403, 396, 392
tests/00-geo-rep/georep-basic-dr-tarssh.t, 811, 814, 817, 4050, 4053
tests/bugs/bug-1368312.t, 815, 816, 811, 813, 403
tests/bugs/distribute/bug-1122443.t, 4050, 407, 403, 815, 816
tests/bugs/glusterd/add-brick-and-validate-replicated- volume-options.t,
814, 816, 817, 812, 815
tests/bugs/replicate/bug-1586020-mark-dirty-for-entry- txn-on-quorum-failure.t,
4049, 812, 814, 405, 392
tests/bitrot/bug-1373520.t, 811, 816, 817, 813
tests/bugs/ec/bug-1236065.t, 812, 813, 815
tests/00-geo-rep/georep-basic-dr-rsync.t, 813, 4046
tests/basic/ec/ec-1468261.t, 817, 812
tests/bugs/glusterd/quorum-validation.t, 4049, 407
tests/bugs/quota/bug-1293601.t, 811, 812
tests/basic/afr/add-brick-self-heal.t, 407
tests/basic/afr/granular-esh/replace-brick.t, 392
tests/bugs/core/multiplex-limit-issue-151.t, 405
tests/bugs/distribute/bug-1042725.t, 405
I think this was caused by a failure to cleanup the mounts from the previous test. It succeeds on retry.
================================================================================ [16:59:12] Running tests in file ./tests/bugs/distribute/bug-1042725.t ./tests/bugs/distribute/bug-1042725.t .. 1..16 Aborting. /mnt/nfs/1 could not be deleted, here are the left over items drwxr-xr-x. 2 root root 6 Jul 31 16:59 /d/backends drwxr-xr-x. 2 root root 4096 Jul 31 16:59 /mnt/glusterfs/0 drwxr-xr-x. 2 root root 4096 Jul 31 16:59 /mnt/glusterfs/1 drwxr-xr-x. 2 root root 4096 Jul 31 16:59 /mnt/glusterfs/2 drwxr-xr-x. 2 root root 4096 Jul 31 16:59 /mnt/glusterfs/3 drwxr-xr-x. 2 root root 4096 Jul 31 16:59 /mnt/nfs/0 drwxr-xr-x. 2 root root 4096 Jul 31 16:59 /mnt/nfs/1 Please correct the problem and try again.
tests/bugs/distribute/bug-1117851.t, 405
tests/bugs/glusterd/rebalance-operations-in-single-node.t, 405
tests/bugs/index/bug-1559004-EMLINK-handling.t, 405
tests/bugs/replicate/bug-1386188-sbrain-fav-child.t, 4048
tests/bugs/replicate/bug-1433571-undo-pending-only-on- up-bricks.t, 813
Thanks,
Shyam
On 07/30/2018 03:21 PM, Shyam Ranganathan wrote:
> Gluster-devel mailing list> On 07/24/2018 03:12 PM, Shyam Ranganathan wrote:
>> 1) master branch health checks (weekly, till branching)
>> - Expect every Monday a status update on various tests runs
>
> See https://build.gluster.org/job/nightly-master/ for a report on
> various nightly and periodic jobs on master.
>
> RED:
> 1. Nightly regression (3/6 failed)
> - Tests that reported failure:
> ./tests/00-geo-rep/georep-basic-dr-rsync.t
> ./tests/bugs/core/bug-1432542-mpx-restart-crash.t
> ./tests/bugs/replicate/bug-1586020-mark-dirty-for-entry- txn-on-quorum-failure.t
> ./tests/bugs/distribute/bug-1122443.t
>
> - Tests that needed a retry:
> ./tests/00-geo-rep/georep-basic-dr-tarssh.t
> ./tests/bugs/glusterd/quorum-validation.t
>
> 2. Regression with multiplex (cores and test failures)
>
> 3. line-coverage (cores and test failures)
> - Tests that failed:
> ./tests/bugs/core/bug-1432542-mpx-restart-crash.t (patch
> https://review.gluster.org/20568 does not fix the timeout entirely, as
> can be seen in this run,
> https://build.gluster.org/job/line-coverage/401/consoleFull )
>
> Calling out to contributors to take a look at various failures, and post
> the same as bugs AND to the lists (so that duplication is avoided) to
> get this to a GREEN status.
>
> GREEN:
> 1. cpp-check
> 2. RPM builds
>
> IGNORE (for now):
> 1. clang scan (@nigel, this job requires clang warnings to be fixed to
> go green, right?)
>
> Shyam
> _______________________________________________
> Gluster-devel@xxxxxxxxxxx
> https://lists.gluster.org/mailman/listinfo/gluster-devel
>
_______________________________________________
maintainers mailing list
maintainers@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/maintainers
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel