You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 27, 2020. It is now read-only.
I spin up a Clearwater Docker deployment and run our live test suite against (see the live-test-docker CI job). The live tests fail reliably. Specifically, about midway through the run, an Ellis request times out. The remaining tests continue to run as normal once the request times out.
I've no idea what's going on here really. There's nothing obvious in the nginx logs or ellis logs. There had been no code changes in any of our repos when this first started happening. I thought we might be using a newer version of another package that ellis depends on, and that was bugged, but I spun up a normal AIO node (no Docker) and didn't reproduce this problem.
Setting to medium priority because it damages our docker story.
The text was updated successfully, but these errors were encountered:
Update on this. We've just spun up a clearwater-docker deployment and run the live tests successfully 13 times in a row (having previously been failing most times). Now we've just failed again, this time with every single Ellis request seemingly timing out.
I spin up a Clearwater Docker deployment and run our live test suite against (see the live-test-docker CI job). The live tests fail reliably. Specifically, about midway through the run, an Ellis request times out. The remaining tests continue to run as normal once the request times out.
I've no idea what's going on here really. There's nothing obvious in the nginx logs or ellis logs. There had been no code changes in any of our repos when this first started happening. I thought we might be using a newer version of another package that ellis depends on, and that was bugged, but I spun up a normal AIO node (no Docker) and didn't reproduce this problem.
Setting to medium priority because it damages our docker story.
The text was updated successfully, but these errors were encountered: