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

[Bug] #2549

Open
0xShankar opened this issue Sep 18, 2024 · 0 comments
Open

[Bug] #2549

0xShankar opened this issue Sep 18, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@0xShankar
Copy link

Improving Reliability of Tests in CI Pipeline (snarkVM)

Issue: Flaky Tests during CI

Description:

I've noticed intermittent test failures in the CI pipeline, particularly around the networking module during stress tests.

These failures seem environment-specific and could be related to race conditions or timing issues within the test suite.

Suggested Improvement:

  1. Introduce Timeouts: For some tests that are highly dependent on network conditions, applying timeouts and ensuring async handling is more robust could reduce the occurrence of flaky tests.
  2. Test Isolation: Consider isolating integration tests from unit tests in separate pipelines. This will help pinpoint whether the issue is network-related or logic-related.
    3.Mock Network Conditions: Integrate a mocking library for network conditions, such as tokio-test, to simulate failures or timeouts without depending on external environments.

These steps should improve the stability of the CI pipeline and reduce the need for reruns.

@0xShankar 0xShankar added the bug Something isn't working label Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant