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

Correct test problems - [merged] #806

Closed
massa-bot opened this issue Nov 11, 2021 · 8 comments
Closed

Correct test problems - [merged] #806

massa-bot opened this issue Nov 11, 2021 · 8 comments

Comments

@massa-bot
Copy link

In GitLab by @damip

Merges damir_clarify_test_problems -> master

@massa-bot
Copy link
Author

In GitLab by @damip

requested review from @gterzian

@massa-bot
Copy link
Author

In GitLab by @damip

assigned to @damip

@massa-bot
Copy link
Author

In GitLab by @damip

@gterzian can you take a look and give me your opinion ?

@massa-bot
Copy link
Author

In GitLab by @damip

changed the description

1 similar comment
@massa-bot
Copy link
Author

In GitLab by @damip

changed the description

@massa-bot
Copy link
Author

In GitLab by @gterzian

Looks like it's working. Did you find out what the underlying reason for the timeouts was and that is is a more direct way of fixing it?

removed the test-threads=1 parameter

Where did you do this? I don't see this change, or the original parameter.

for many simple unit tests we could afford removing #[serial] to accelerate the pipeline

In the light of https://gitlab.com/massalabs/massa-network/-/merge_requests/318, to keep it simple we should either use multiple threads per tests(threaded tokio runtime), and run these tests serially, or use a single-threaded runtime(the default) with tests running in parallel. Using a threaded runtime and parallel tests is likely to make things more complicated with setting/sharing the serialization context.

@massa-bot
Copy link
Author

In GitLab by @damip

approved this merge request

@massa-bot
Copy link
Author

In GitLab by @damip

mentioned in commit 11ec775

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

No branches or pull requests

1 participant