Use pytest in integration test #715
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jimexist
force-pushed
the
use-pytest
branch
4 times, most recently
from
fe7bc92 to
d62443b
Compare
alamb
approved these changes
Jul 12, 2021
Contributor
alamb
left a comment
alamb
left a comment
There was a problem hiding this comment.
Looks good to me
The test is also looking good: https://github.com/apache/arrow-datafusion/pull/715/checks?check_run_id=3044045000#step:8:18 👍
| # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
| # See the License for the specific language governing permissions and | ||
| # limitations under the License. | ||
| pytest |
jorgecarleitao
approved these changes
Jul 12, 2021
houqp
approved these changes
Jul 13, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #673
Rationale for this change
What changes are included in this PR?
Are there any user-facing changes?