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

Run the tests in the subcrate #51

Merged
merged 3 commits into from
Feb 20, 2020
Merged

Conversation

ChunMinChang
Copy link
Member

The test in the sub-crate, coreaudio-sys-utils, aren't run in both local device and Travis CI server. Those tests in the coreaudio-sys-utils should also be run with the sanitizers. It will be easier to identify the problem (if any) is in the underlying system API implemented in the sub-crate, or it's in the main crate, by running the tests in the sub crate.

Running those tests is helpful to diagnose the problem, or narrow down the scope of the problem at least. For example, there are memory leaks found by running MemorySanitier with the tests in the coreaudio-sys-utils. It indicates the memory is leaking when calling the underlying APIs. It's helpful to address the leak issue found in #45.

On the other hand, the format check and the lints/clippy check should always be run, instead of running in Travis CI server only. It makes sure every commit follows the Rust coding style properly.

The format check should always be run, in main crate and sub crate, not
only in Travis CI server only. The format checks and lints(clippy)
checks should be moved from .travis.yml to run_tests.sh.
@ChunMinChang ChunMinChang requested a review from padenot February 18, 2020 23:36
@ChunMinChang ChunMinChang self-assigned this Feb 18, 2020
@ChunMinChang ChunMinChang merged commit 54d950a into trailblazer Feb 20, 2020
@ChunMinChang ChunMinChang deleted the run-subcrate-tests branch February 26, 2020 22:10
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