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

Split out MixedVecSpec integration tests #3373

Merged
merged 1 commit into from Jun 21, 2023
Merged

Conversation

jackkoenig
Copy link
Contributor

This will speed up the typical test flow by separating the execution driven tests out.

Also rename the file containing VecIntegrationSpec to match the class name.

Reviewer Checklist (only modified by reviewer)

  • Did you add the appropriate labels? (Select the most appropriate one based on the "Type of Improvement")
  • Did you mark the proper milestone (Bug fix: 3.5.x or 3.6.x depending on impact, API modification or big change: 5.0.0)?
  • Did you review?
  • Did you check whether all relevant Contributor checkboxes have been checked?
  • Did you do one of the following when ready to merge:
    • Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
    • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

@jackkoenig jackkoenig added the Internal Internal change, does not affect users, will be included in release notes label Jun 21, 2023
This will speed up the typical test flow by separating the execution
driven tests out.

Also rename the file containing VecIntegrationSpec to match the class
name.
@jackkoenig jackkoenig merged commit 5e13128 into main Jun 21, 2023
13 checks passed
@jackkoenig jackkoenig deleted the mixed-vec-integration-spec branch June 21, 2023 22:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Internal Internal change, does not affect users, will be included in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant