Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Contract tests fail randomly

Description

Our contract-test job fails randomly. Sometimes because of empty test result xml file, sometimes totally random tests fails and after rebuild - another or everything passed. Also, the duration displayed on Jenkins is distorted - it always shows fewer minutes than it actually takes. The third issue is that sometimes requisition contract tests take too long (like 45min) because they get stuck at examples.

Acceptance Criteria:

  • look whether there are still no logs for the requisition service and add them

  • all issues causing random failures are fixed

  • proper duration is displayed on Jenkins

  • solution should be discussed on Tech Debt channel / tech committee call / tech group

Attachments

2

Confluence content

mentioned on

Activity

Show:
Sebastian Brudziński
August 1, 2018 at 12:36 PM

The random and not random failures have been resolved. Moving to done.

Mateusz Kwiatkowski
July 24, 2018 at 4:47 PM

I'll be on the leave for few days so I'm assigning this ticket to you. I was searching through logs to find some solution and nothing came to me, logs from services are actually not there from what I see (at least from fulfillment and requisition). For now requisition contract tests are hanging up after tests both locally and on Jenkins, not sure what causes that, but I was able to successfully run requisition contract test from v3.3.1 branch with current services versions. I've only changed requisition docker compose file to one from master branch and I've increased wait time from 5000ms to 60sec in gradle.build. I would then, that probably some changes to requisition contract tests made after 3.3 is causing that, rather than something in requisition service (or any other).

Łukasz Lewczyński
July 19, 2018 at 11:14 AM

From what I see the logs are still not visible. Probably missing entry in logback configuration but it could be something else.

Sebastian Brudziński
July 19, 2018 at 11:12 AM

do you know if logs from the requisition service are still not displayed or what the cause for this is?

Łukasz Lewczyński
June 29, 2018 at 12:31 PM
(edited)

I changed priority to blocker because now the requisition contract tests does not pass. There is no error message, nothing in logs, they just simple stop in the middle and we have to kill the CI job. Because of that we can't verify changes in requisition and stock management services

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

Details

Assignee

Reporter

Labels

Story Points

Original estimate

Time tracking

2w 2h 30m logged1h remaining

Sprint

None

Fix versions

Priority

Time Assistant

Created June 15, 2018 at 9:02 AM
Updated August 15, 2018 at 9:57 PM
Resolved August 1, 2018 at 12:36 PM