Skip to content

Fix coverage tests #5735

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix coverage tests #5735

wants to merge 2 commits into from

Conversation

rdettai
Copy link
Collaborator

@rdettai rdettai commented Apr 7, 2025

Description

test_merge_executor_controlled_directory_kill_switch is failing since this change

How was this PR tested?

Describe how you tested this PR.

@rdettai rdettai self-assigned this Apr 7, 2025
@rdettai rdettai force-pushed the fix-coverage-tests branch 2 times, most recently from 29a929a to 8f582a0 Compare April 7, 2025 12:20
@rdettai
Copy link
Collaborator Author

rdettai commented Apr 7, 2025

Comment on lines +336 to -344
fail::cfg(
"after-merge-split",
"panic(merge should be failed by directory kill switch)",
)
.unwrap();
merge_executor_mailbox.send_message(merge_scratch).await?;
before_universe_kill.wait();
universe.kill();
after_universe_kill.wait();
fail::cfg("before-merge-split", "off").unwrap();

let (exit_status, _) = merge_executor_handle.join().await;
assert!(matches!(exit_status, ActorExitStatus::Failure(_)));
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@fulmicoton-dd I know you wrote this a long time ago, but do you happen to remember why you were testing the merge_executor_handle.join() result instead of using a panic failpoint?

Note: the actor exit status is now Killed instead of Failure because since #5704, merge failures return Ok() with an error!. log instead of failing the actor. But this is not what this test is about, hence the proposed change.

@rdettai rdettai requested a review from fulmicoton-dd April 8, 2025 11:43
@rdettai rdettai force-pushed the fix-coverage-tests branch from eba9dbb to 672b689 Compare April 24, 2025 12:30
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.

2 participants