-
Notifications
You must be signed in to change notification settings - Fork 56
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
Cleanup tests, run everything (except hdfs) #284
Conversation
@@ -59,7 +59,7 @@ jobs: | |||
override: true | |||
- uses: Swatinem/rust-cache@v2 | |||
- name: test | |||
run: cargo test --verbose --all-features | |||
run: cargo test --workspace --verbose --all-features -- --skip read_table_version_hdfs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the hdfs test starts up a java environment which takes >1m and makes the whole test suite take much longer, so I'm skipping it for now (could become a nightly test)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
created #285 to track
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@@ -59,7 +59,7 @@ jobs: | |||
override: true | |||
- uses: Swatinem/rust-cache@v2 | |||
- name: test | |||
run: cargo test --verbose --all-features | |||
run: cargo test --workspace --verbose --all-features -- --skip read_table_version_hdfs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
created #285 to track
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGMT
Make sure our CI runs all the tests for the whole workspace.
Also fix some failing tests in
ffi
due to either mistakes in the doc comment or slight compiler output changes.