test(ci): RUN_SERIAL state_transport_ipc_test, the suite #121 missed - #325
Merged
Merged
Conversation
#121 moved the fork()+IPC multiprocess tests off the parallel ctest scheduler because their socket and replication windows get starved under load, producing failures that say nothing about the code. It covered state_exec_multiprocess_test and state_multiprocess_ipc_test. state_transport_ipc_test has the same profile -- real Unix-domain sockets driven with poll() timeouts -- and was left on the parallel scheduler. It still flakes: StateTransportIpcTest.TwoEndpointConvergence was the single failure out of 2739 tests on an unrelated PR (#324, an SDF header fix that touches nothing near state or IPC), which is what surfaced the gap. Same one-line treatment as its two siblings.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#121 moved the
fork()+IPC multiprocess tests off the parallel ctest scheduler, because their socket and replication windows get starved under load and fail assertions that say nothing about the code. It covered two suites:state_transport_ipc_testhas the same profile and was missed. It drives real Unix-domain sockets withpoll()timeouts, and it is still on the parallel scheduler.It still flakes.
StateTransportIpcTest.TwoEndpointConvergencewas the single failure out of 2739 tests on #324 — a PR whose diff is an SDF header macro fix, two comment removals, a version variable and a recipe, nothing within reach of state or IPC. That is what surfaced the gap.Same one-line treatment as its two siblings. Worth landing ahead of the other open PRs so they stop inheriting the flake.