Update tests related to the next Meilisearch release (v1.6.0) #900
Conversation
This file contains 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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #900 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 13 13
Lines 752 752
=========================================
Hits 752 752 ☔ View full report in Codecov by Sentry. |
9 tasks
curquiza
added
the
skip-changelog
curquiza
force-pushed
the
bump-meilisearch-v1.6.0
branch
from
7ac5a8b to
58ad336
Compare
sanders41
reviewed
Jan 11, 2024
meili-bors bot
added a commit
that referenced
this pull request
Jan 15, 2024
900: Changes related to the next Meilisearch release (v1.6.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#294 This PR: - gathers the changes related to the next Meilisearch release (v1.6.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.6.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.6.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <74670311+meili-bot@users.noreply.github.com> Co-authored-by: curquiza <clementine@meilisearch.com> Co-authored-by: Clémentine U. - curqui <clementine@meilisearch.com> Co-authored-by: Paul Sanders <psanders1@gmail.com>
curquiza
added
maintenance
curquiza
changed the title
|
Build failed: |
|
Code coverage! I hate this tool!!! 😅 |
|
bors merge |
meili-bors bot
added a commit
that referenced
this pull request
Jan 15, 2024
900: Update tests related to the next Meilisearch release (v1.6.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#294 This PR: - gathers the changes related to the next Meilisearch release (v1.6.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.6.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.6.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <74670311+meili-bot@users.noreply.github.com> Co-authored-by: curquiza <clementine@meilisearch.com> Co-authored-by: Clémentine U. - curqui <clementine@meilisearch.com> Co-authored-by: Paul Sanders <psanders1@gmail.com>
|
Build failed: |
|
bors merge |
meili-bors bot
added a commit
that referenced
this pull request
Jan 15, 2024
900: Update tests related to the next Meilisearch release (v1.6.0) r=curquiza a=meili-bot Related to this issue: meilisearch/integration-guides#294 This PR: - gathers the changes related to the next Meilisearch release (v1.6.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.6.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.6.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <74670311+meili-bot@users.noreply.github.com> Co-authored-by: curquiza <clementine@meilisearch.com> Co-authored-by: Clémentine U. - curqui <clementine@meilisearch.com> Co-authored-by: Paul Sanders <psanders1@gmail.com>
|
Build failed: |
Yes! I have been fighting with it all day. I've looked for alternatives but so far I have not found anything. |
|
@sanders41 do you agree I merge manually even if the tests are failing? We can also remove completely code coverage until we find another working tool cc: @brunoocasali |
Yes, I agree. These failures are clearly codecov related and all the tests are passing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to this issue: meilisearch/integration-guides#294
This PR:
This PR is auto-generated for the pre-release week purpose.