Skip to content

Conversation

@evgeny-leksikov
Copy link
Contributor

@evgeny-leksikov evgeny-leksikov commented Nov 7, 2025

What?

Add new tests for SyncManager implementation.

Why?

#828 (comment)

NOTE: marked as a draft since the PR #1003 improves sync_manager, so this PR will require to resolve conflicts.

@github-actions
Copy link

github-actions bot commented Nov 7, 2025

👋 Hi evgeny-leksikov! Thank you for contributing to ai-dynamo/nixl.

Your PR reviewers will review your contribution then trigger the CI to test your changes.

🚀

@evgeny-leksikov
Copy link
Contributor Author

/build

gleon99
gleon99 previously approved these changes Nov 20, 2025
roiedanino
roiedanino previously approved these changes Nov 20, 2025
@evgeny-leksikov
Copy link
Contributor Author

temporary rebased on top of #829

Signed-off-by: Evgeny Leksikov <[email protected]>
@evgeny-leksikov
Copy link
Contributor Author

/build

Comment on lines +43 to +54
let data_calls = Rc::new(Cell::new(0));
let backend_calls = Rc::new(Cell::new(0));

let data = DummyData {
value: Cell::new(0),
data_calls: data_calls.clone(),
should_fail: Cell::new(false),
};
let backend = DummyBackend {
sync_calls: backend_calls.clone(),
};
let mgr = SyncManager::new(data, backend);
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's try to reduce code duplication in the initialization of those tests, maybe we can use some kind of default constructors that will populate those fields:

let data = DummyData::default();
let backend = DummyBackend::default();
// and so on

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants