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

Fix random failure due to parallelism races in 10_ tests #4878

Merged
merged 1 commit into from
Dec 6, 2024

Conversation

dorinhogea
Copy link
Contributor

The rows can arrive in different order, if order is only partially specified, or if we select less than total number of rows, due to parallelism in shard processing. Only test set 10 is affected, the other are properly set.

Copy link

@roborivers roborivers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Coding style check: Success ✓.
Smoke testing: Success ✓.
Cbuild submission: Success ✓.
Regression testing: 8/589 tests failed ⚠.

The first 10 failing tests are:
lostwrite [setup failure]
sc_truncate_multiddl_generated [setup failure]
comdb2sys_queueodh_generated [setup failure]
comdb2sys [setup failure]
basic_snapshot_generated [setup failure]
biginplace [setup failure]
sc_transactional_rowlocks_generated
snap_ha_retry_newsi_generated

@dorinhogea
Copy link
Contributor Author

@aakash10292 thank you

@dorinhogea dorinhogea merged commit d5b01f5 into bloomberg:main Dec 6, 2024
1 check passed
@dorinhogea dorinhogea deleted the fixunionparaltest branch December 6, 2024 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants