[FOLIO-2079] folio-perf-test "Timeout has been exceeded" after 3 hours Created: 06/Jun/19  Updated: 03/Jun/20  Resolved: 10/Jun/19

Status: Closed
Project: FOLIO
Components: Continuous Integration
Affects versions: None
Fix versions: None

Type: Bug Priority: P2
Reporter: Julian Ladisch Assignee: Hongwei Ji
Resolution: Done Votes: 0
Labels: ci, platform-backlog, ui-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by OKAPI-740 "Wait for lock" when enabling module ... Closed
Sprint: CP: sprint 65
Story Points: 0.5
Development Team: Core: Platform

 Description   

Since May 30 https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/ takes more than 3 hours and times out.
Before it took 1.5 hours.



 Comments   
Comment by Jakub Skoczen [ 07/Jun/19 ]

Hongwei Ji any idea what goes wrong with the perf test job? Looks like there is a lot of timouts related to cloudformation in the Console Output.

Comment by Hongwei Ji [ 07/Jun/19 ]

See https://folio-org.atlassian.net/browse/OKAPI-740. We will need to wait till Okapi 2.30.0 is released and deployed on snapshot site.

Comment by Hongwei Ji [ 07/Jun/19 ]

I investigated the cause a few days earlier and opened OKAPI-740 Closed . Once the new Okapi is released, this should be resolved automatically.

Comment by Hongwei Ji [ 07/Jun/19 ]

BTW, added a parameter to specify which version Okapi to run. Kicked off a build with Okapi 2.30.0 and it finished. See https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/357/

Comment by Hongwei Ji [ 10/Jun/19 ]

Okapi 2.30.0 was released. Build can finish now.

Generated at Thu Feb 08 23:18:03 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.