Bug 1218458 - canLimitConcurrentRestRequestsPerAPIKey test unstable
Summary: canLimitConcurrentRestRequestsPerAPIKey test unstable
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Zanata
Classification: Retired
Component: Maintainability
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Patrick Huang
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-05 00:40 UTC by Damian Jansen
Modified: 2015-07-31 01:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-31 01:19:59 UTC
Embargoed:


Attachments (Terms of Use)

Description Damian Jansen 2015-05-05 00:40:57 UTC
Description of problem:
The RateLimitRestAndUITest.canLimitConcurrentRestRequestsPerAPIKey test is unstable.  It depends on Zanata being too slow to handle the series of requests thrown at it, but if it's fast enough (or the test events are too slow) the test will fail.

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

How reproducible:
Intermittent

Additional info:
Error Message

Expecting:
 <[201, 201, 201, 201, 201]>
to contain:
 <[201, 201, 201, 201, 429]>
but could not find:
 <[429]>
Stacktrace

java.lang.AssertionError: 
Expecting:
 <[201, 201, 201, 201, 201]>
to contain:
 <[201, 201, 201, 201, 429]>
but could not find:
 <[429]>

at org.zanata.feature.misc.RateLimitRestAndUITest.canLimitConcurrentRestRequestsPerAPIKey(RateLimitRestAndUITest.java:259)

Comment 1 Zanata Migrator 2015-07-31 01:19:59 UTC
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-434


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