-
Notifications
You must be signed in to change notification settings - Fork 44
SPOC-345: Move zodan sync test to separate github action #274
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
Conversation
657e32a to
35a6b4c
Compare
Designed to be highly competitive, this test consumes more CPU, disk, and memory resources than usual. To let people pass basic checks on their ongoing commits faster, turn off this test in the schedule and separate it as a GitHub action. Also, it appears that we copied Spock into the base image. Hence, the 'step-1' Docker image might use oldish versions of the patches.
There are some corner cases that, at least for now, need to involve both the publisher and the subscriber when we try to determine whether all the data is replicated (synchronisation has finished). So, rewrite the sync code to sync_event/wait calls. It seems that if we improve wait functions a little, it may serve to multiple purposes. For example, we may add sync_event to the wait function, replace integer timeouts with the Interval type, and introduce 'verbose' mode. And yes, rewrite it as a function.
|
@pct960, doing this, I found an issue with the base image creation Dockerfile. If you can, please take a look - just to understand how worse it is and if my fix is correct. |
pct960
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly looks good. Only some minor changes are needed.
I couldn't get around to running the workflow, however.
Will do it after you merge.
There are me also fix the issue with base image ...