[MXS-1843] Sporadic test_logthrottling failures on Ubuntu Created: 2018-05-02  Updated: 2018-06-15  Resolved: 2018-05-14

Status: Closed
Project: MariaDB MaxScale
Component/s: Core
Affects Version/s: 2.2.5
Fix Version/s: 2.2.6

Type: Bug Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

Ubuntu Trusty and Xenial


Sprint: MXS-SPRINT-57

 Description   

18/50 Test #18: test_logthrottling .................***Failed   71.43 sec
Logging 100 messages with throttling as {0, 0, 0},
Status: expected 400 messages, found 400.
Logging 100 messages with throttling as {10, 2000, 5000},
Status: expected 10 messages, found 10.
Sleeping 7 seconds.
Logging 100 messages with throttling as {10, 2000, 5000},
Status: expected 10 messages, found 10.
Sleeping 1 seconds.
Logging 100 messages with throttling as {10, 2000, 5000},
Status: expected 0 messages, found 0.
Sleeping 6 seconds.
Logging 100 messages with throttling as {20, 1000, 5000},
Status: expected 20 messages, found 96.
Logging 20 messages with throttling as {10, 1000, 5000},
Status: expected 80 messages, found 80.
Logging 20 messages with throttling as {10, 1000, 5000},
Status: expected 81 messages, found 81.
Logging 20 messages with throttling as {10, 1000, 5000},
Status: expected 80 messages, found 80.
Closed /tmp/maxscale.log



 Comments   
Comment by markus makela [ 2018-05-02 ]

Ran 100 iterations of the test on a Ubuntu Trusty docker image and wasn't able to reproduce it. Trying with a VM next.

Comment by markus makela [ 2018-05-08 ]

Tested on a Ubunty Trusty VM, was not able to reproduce.

Comment by markus makela [ 2018-05-14 ]

The test now creates a separate log directory for each test run. This should prevent problems caused by running two simultaneous tests.

Generated at Thu Feb 08 04:09:48 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.