Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Flaky e2e integration test: Sentinel transition error log error for unknown transition: #8592

Closed
dianabarsan opened this issue Sep 27, 2023 · 1 comment · Fixed by #8623
Closed

Flaky e2e integration test: Sentinel transition error log error for unknown transition: #8592

dianabarsan opened this issue Sep 27, 2023 · 1 comment · Fixed by #8623
Assignees
@dianabarsan
Labels
Flaky Indicates a flaky or unreliable test Testing Affects how the code is tested Type: Technical issue Improve something that users won't notice
Milestone
4.5.0

Comments

@dianabarsan
Copy link
Member

Describe the issue
Example failure: https://github.com/medic/cht-core/actions/runs/6322503058/job/17168590936#step:16:7569
@dianabarsan dianabarsan added Type: Technical issue Improve something that users won't notice Testing Affects how the code is tested Flaky Indicates a flaky or unreliable test labels Sep 27, 2023
@dianabarsan dianabarsan self-assigned this Oct 5, 2023
@dianabarsan
Copy link
Member Author

I managed to replicate this locally. I believe this is a problem with getting docker logs.
The logs I got in the test are:

[
  '2023-10-06T09:18:52.300 DEBUG: change event on doc e2e_contact_test_id seq 5391-g1AAAARFeJyl0j1OwzAUwHHTIrGwIu6ABNj5wM4E4ga08QHi50RRFOjEDBdgQarEjgStB67AKTpxg56B1rw6HjKkLJ6eFMU_Pf3tlhByXI81OYXZI9Ra3fh5zi7aGRRtiz-MCqJOpMybeqwIOfi6x29HwKMqyej-k4Nq3FN3plRnxiw9nDs44UwnItt_eBCO-jCaRl1bu-3g0cTBZQwsTYc2jv6B-x12plW49dRvfOlgWgpesqAUaOaqMWbh4XcHZzGvaJKEpEBzqZ6s3fgUrx0shKBlGZICze3DIZlIOfc73zo6LTlloANioDpFFccn3qPH5w5nCnQaFQFBUF2giuPX2m-Pv3QPDwpBNQREQXWDKo47KVcef-6yQFIA8LAsGHuF48OYtb_OH4frq7jimoVlwdhrHPjCrd_8zeERp4LC0CP0QPMHF9pWhQ ',
  '2023-10-06T09:18:52.530 INFO: Reloading configuration ',
  '2023-10-06T09:18:52.537 WARN: Disabled transition "update_clinics" ',
  '2023-10-06T09:18:52.537 WARN: Disabled transition "self_report" ',
  '2023-10-06T09:18:52.537 WARN: Disabled transition "registration" ',
  '2023-10-06T09:18:52.537 WARN: Disabled transition "accept_patient_reports" ',
  '2023-10-06T09:18:52.537 WARN: Disabled transition "accept_case_reports" ',
  ''

Clearly lacking lines, which were actually logged.
I believe this is caused by adding two listeners to the same container log at the same time, and some race condition preventing one from getting output.

@dianabarsan dianabarsan mentioned this issue Oct 9, 2023
Merged
5 tasks
@dianabarsan dianabarsan linked a pull request Oct 9, 2023 that will close this issue
chore(#8592): stabilize unknown transition test #8623
Merged
5 tasks
dianabarsan added a commit that referenced this issue Oct 9, 2023
@dianabarsan
chore(#8592): stabilize unknown transition test (#8623)
4ff307d 
#8592
@dianabarsan dianabarsan added this to the 4.5.0 milestone Oct 9, 2023
Benmuiruri pushed a commit that referenced this issue Oct 26, 2023
@dianabarsan @Benmuiruri
chore(#8592): stabilize unknown transition test (#8623)
c6a5ee9 
#8592
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dianabarsan dianabarsan

Labels
Flaky Indicates a flaky or unreliable test Testing Affects how the code is tested Type: Technical issue Improve something that users won't notice
Projects
None yet
Milestone
4.5.0
Development

Successfully merging a pull request may close this issue.

chore(#8592): stabilize unknown transition test medic/cht-core
1 participant
@dianabarsan