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.

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

test(ci): fix flake AMQ214015 Failed to execute connection life cycle #2378

Closed
petermetz opened this issue Apr 7, 2023 · 1 comment
Closed
Labels
bug Something isn't working Flaky-Test-Automation Issues related to test stability (which is a long running issue that can never fully be solved) Tests Anything related to tests be that automatic or manual, integration or unit, etc. Weaver Tasks related to the future of Cactus & Weaver together.

Comments

@petermetz
Copy link
Contributor

Describe the bug

The .github/workflows/test_weaver-data-sharing.yml CI job occasionally fails (e.g. flaky test)

Not sure at all if this AMQ error code is actually the root cause or just some inconsequential error log, but at the end of the job log it says so something is definitely up.

2023-04-07T00:55:43.0880902Z Passed 10/12 Tests.
2023-04-07T00:55:43.0885113Z ##[error]Process completed with exit code 1.

To Reproduce

Run the CI until it fails randomly. Eventually it will.

Expected behavior

Test is consistently succeeding in all the different environments.

Logs/Stack traces

2023-04-07T00-31-21-weaver-data-sharing-local-crash-ci.log

Cloud provider or hardware configuration:

GitHub/BuildJet

Operating system name, version, build:

Ubuntu-20.04

Hyperledger Cactus release version or commit (git rev-parse --short HEAD):

main

cc: @VRamakrishna @sandeepnRES

@petermetz petermetz added bug Something isn't working Flaky-Test-Automation Issues related to test stability (which is a long running issue that can never fully be solved) Tests Anything related to tests be that automatic or manual, integration or unit, etc. Weaver Tasks related to the future of Cactus & Weaver together. labels Apr 7, 2023
@sandeepnRES
Copy link
Contributor

Just to correct, AMQ error code isn't the cause, that step is still passing as per logs.
Error was: 2023-04-07T00:54:54.5670941Z 2023-04-07 00:54:54 �[31merror�[39m [fabric-cli]: Error verifying and storing state: Error: InteropFlow remote view request error: Error: InteropFlow relay response error: Error: Error: State error: Error: Timeout: State is still pending.
Timeout error, which I think is resolved with PR #2438 , which increases the timeout value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Flaky-Test-Automation Issues related to test stability (which is a long running issue that can never fully be solved) Tests Anything related to tests be that automatic or manual, integration or unit, etc. Weaver Tasks related to the future of Cactus & Weaver together.
Projects
None yet
Development

No branches or pull requests

2 participants