test/ghostflow: do not hold the `data` lock while sending updates

If the channel between the HostingService and the actual host is full, the read-only data lock ends up blocking the host from performing its handling of events where it needs the write lock.

requested review from @brad.king

added 1 commit

• 7395d563 - gitlab-ci: remove retry on test jobs

Compare with previous version

added 3 commits

• 47611592 - test/ghostflow: do not hold the `data` lock while sending updates
• 44f5b019 - test/ghostflow: make sure we don't hold the lock while updating
• 5434357c - gitlab-ci: remove retry on test jobs

Compare with previous version

added 3 commits

• 6ca53767 - test/ghostflow: do not hold the `data` lock while sending updates
• 4f579c45 - test/ghostflow: make sure we don't hold the lock while updating
• 5c3ebdd3 - gitlab-ci: remove retry on test jobs

Compare with previous version

added 3 commits

• 974a3833 - test/ghostflow: do not hold the `data` lock while sending updates
• f6eb477c - test/ghostflow: make sure we don't hold the lock while updating
• ec9a8b80 - gitlab-ci: remove retry on test jobs

Compare with previous version

Warnings:

• please consider adding a changelog entry in the CHANGELOG.md file.

The warnings do not need to be fixed, but it is recommended to do so.

+1

Do: merge

merged

mentioned in commit e1c6c0b8