Bug 1718191 - Regression: Intermittent test failure for quick-read-with-upcall.t
Summary: Regression: Intermittent test failure for quick-read-with-upcall.t
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: quick-read
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-07 08:22 UTC by Amar Tumballi
Modified: 2020-03-12 12:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-12 12:34:24 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22836 0 None Open tests/quick-read-upcall: mark it bad 2019-06-07 08:49:42 UTC

Description Amar Tumballi 2019-06-07 08:22:54 UTC
Description of problem:
While running regression, quick-read-with-upcall.t script fails intermittently.

Please debug and fix the problem.

Version-Release number of selected component (if applicable):
master

How reproducible:
1/10

Steps to Reproduce:
1. Submit a patch and run regression.


Additional info:

Error is normally like below:

08:59:24 ok  11 [     10/      3] <  36> 'write_to /mnt/glusterfs/0/test.txt test-message1'
08:59:24 ok  12 [     10/      6] <  37> 'test-message1 cat /mnt/glusterfs/0/test.txt'
08:59:24 ok  13 [     10/      4] <  38> 'test-message0 cat /mnt/glusterfs/1/test.txt'
08:59:24 not ok  14 [   3715/      6] <  45> 'test-message1 cat /mnt/glusterfs/1/test.txt' -> 'Got "test-message0" instead of "test-message1"'
08:59:24 ok  15 [     10/    162] <  47> 'gluster --mode=script --wignore volume set patchy features.cache-invalidation on'
08:59:24 ok  16 [     10/    148] <  48> 'gluster --mode=script --wignore volume set patchy performance.qr-cache-timeout 15'

Comment 1 Worker Ant 2019-06-07 08:29:08 UTC
REVIEW: https://review.gluster.org/22836 (tests/quick-read-upcall: mark it bad) posted (#1) for review on master by Amar Tumballi

Comment 2 Worker Ant 2019-06-07 08:49:43 UTC
REVIEW: https://review.gluster.org/22836 (tests/quick-read-upcall: mark it bad) merged (#2) on master by Amar Tumballi

Comment 4 Worker Ant 2020-03-12 12:34:24 UTC
This bug is moved to https://github.com/gluster/glusterfs/issues/908, and will be tracked there from now on. Visit GitHub issues URL for further details


Note You need to log in before you can comment on or make changes to this bug.