Skip to content

Dvirdu_set_7.99.0_version_and_test_unstable#4997

Merged
DvirDukhan merged 2 commits into8.0from
dvirdu_set_7.99.0_version_and_test_unstable
Sep 11, 2024
Merged

Dvirdu_set_7.99.0_version_and_test_unstable#4997
DvirDukhan merged 2 commits into8.0from
dvirdu_set_7.99.0_version_and_test_unstable

Conversation

@DvirDukhan
Copy link

Describe the changes in the pull request

A clear and concise description of what the PR is solving, including:

  1. The current state briefly
  2. What is the change
  3. Adding the outcome (changed state)

Which issues this PR fixes

  1. #...
  2. MOD...

Main objects this PR modified

  1. ...
  2. ...

Mark if applicable

  • This PR introduces API changes
  • This PR introduces serialization changes

Copy link
Collaborator

@GuyAv46 GuyAv46 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we don’t need the tag we can skip this job in both flows

@codecov
Copy link

codecov bot commented Sep 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (8.0@54be2d5). Learn more about missing BASE report.

Additional details and impacted files
@@          Coverage Diff           @@
##             8.0    #4997   +/-   ##
======================================
  Coverage       ?   86.13%           
======================================
  Files          ?      192           
  Lines          ?    34416           
  Branches       ?        0           
======================================
  Hits           ?    29645           
  Misses         ?     4771           
  Partials       ?        0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@DvirDukhan DvirDukhan force-pushed the dvirdu_set_7.99.0_version_and_test_unstable branch from 767c3c9 to 0cfe81f Compare September 10, 2024 19:01
@DvirDukhan DvirDukhan added this pull request to the merge queue Sep 10, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Sep 10, 2024
@DvirDukhan DvirDukhan added this pull request to the merge queue Sep 11, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Sep 11, 2024
@DvirDukhan DvirDukhan added this pull request to the merge queue Sep 11, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Sep 11, 2024
@DvirDukhan DvirDukhan added this pull request to the merge queue Sep 11, 2024
Merged via the queue into 8.0 with commit 0a04739 Sep 11, 2024
@DvirDukhan DvirDukhan deleted the dvirdu_set_7.99.0_version_and_test_unstable branch September 11, 2024 10:40
kei-nan pushed a commit that referenced this pull request Sep 24, 2024
github-merge-queue bot pushed a commit that referenced this pull request Sep 26, 2024
* MOD-7596: Add mirroring support (#4937)

* * initial commit

* * Use RediSearch branch mirroring fork

* * Code Review - Round #1

* MOD-7695: Decide Ubuntu Runner Using Variable (#4975)

* * initial commit

* * code review

* Dvirdu_set_7.99.0_version_and_test_unstable (#4997)

* 7.99.0

* redis unstable tests

* CP single build path

* Fix benchmark to use new build path (#5026)

* Fix benchmark to use new build path

* Take Raz's fix for benchmarks

* fix default module path

* make benchmark fail

* fix path

* fail external flow

* remove fail fast and continue on error

* addressing CR

* Splitting the standalone work among 6 groups. Only profile if explictly enabled. Only run >4 primaries if extended if enabled.

* Specify name of benchmark step on GH flow

* Using perf-cto-base-image-ubuntu20.04-redis-7.4.0-tuned-latency on spot instances as well.

* Fixed RedisJSON module path on benchmark setup. Enforcing ReJSON module to be present

* Changing from 6 to 9 oss-standalone runners to achieve a time for full feedback < 30min

* MODULE_FILE not working on Prepare ReJSON Module: using default location

* Using redisbench-admin >= 0.11.3 due to multi-module issue

* Using redisbench-admin >= 0.11.3 due to multi-module issue

* Added missing --allowed-setups info for oss-standalone config

* redisbench-admin >= 0.11.4

* Remove vecsim-ann-benchmarks_LOAD_1c_redisearch-hnsw_glove-200-angular_M-4.yml

* Using redisbench-admin >= 0.11.5 due to ssh timeout issues on heavy benchmarks or heavy prunning at the end

* Increasing concurrency of standalone benchmarks to reduce time to feedback

* redisbench-admin >= 0.11.6. removed unstable test vecsim-ann-benchmarks_QUERY_1c_redisearch-hnsw_glove-200-angular_M-4

* redisbench-admin >= 0.11.7. running cluster tests faster and also ensuring we use a redisbench-admin with keepalive on ssh tunnels

* Removed search-ftsb-10K-enwiki_abstract-hashes-term-withoutsuffix-trie from cluster tests due to keyspace error check

* Removed search-ftsb-1M-enwiki_abstract-hashes-fulltext-simple-1word-query-non-sortable from cluster tests due to client error. created RediSearch/ftsb#97

* Not running *.rdb based benchmarks on cluster due to orphaned keys (redis/redis#9506)

---------

Co-authored-by: fcostaoliveira <[email protected]>

* rebase 8.0

---------

Co-authored-by: kei-nan <[email protected]>
Co-authored-by: DvirDukhan <[email protected]>
Co-authored-by: fcostaoliveira <[email protected]>
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.

3 participants