Investigate contract test failures on Jenkins

Description

Contract Tests are failing randomly on being unable to connect with an auth service instance (and probably would not connect to any of them, since auth is just first in queue). However, this seems to be happening only on master instance.

This might possibly be some kind of container conflict, or machine setup, that blocks the tests from completing.

Good start point might be checking consul state during the build, or nginx/consul-template logs.

Environment

None

QAlity Plus - Test Management

Checklists

Activity

Paweł Gesek 
February 2, 2017 at 3:17 PM

It was auth was killed 99% of time but it would also ocassionaly happen to reference data. It might just be the order that services would start up, or auth was using more resources due to starting up OAuth beans?

Josh Zamor 
February 1, 2017 at 8:05 PM

Hey , why did the memory issue cause timeouts to auth?

Paweł Gesek 
January 27, 2017 at 3:19 PM

After setting memory limits, the build seems stable. I am closing this and will keep an eye out for any potential issues.

Paweł Nawrocki 
January 23, 2017 at 6:20 PM

the problem is still not resolved.

Sebastian Brudziński 
January 19, 2017 at 2:45 PM

please verify whether this is still an issue. If not, please dead this.

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Story Points

Original estimate

Time tracking

1d 5h logged2d 3h remaining

Components

Sprint

Fix versions

Priority

Time Assistant

Created January 5, 2017 at 2:28 PM
Updated March 22, 2018 at 12:38 PM
Resolved January 27, 2017 at 3:19 PM