MOD-7543 purge readies from sanitizer flow#4726
Conversation
83344a3 to
4eed00c
Compare
6f1e992 to
5176130
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4726 +/- ##
==========================================
- Coverage 86.50% 86.50% -0.01%
==========================================
Files 195 195
Lines 34818 34818
==========================================
- Hits 30121 30120 -1
- Misses 4697 4698 +1 ☔ View full report in Codecov by Sentry. |
| type: string | ||
| required: true | ||
| get-redis: | ||
| type: string |
There was a problem hiding this comment.
This new parameter is not passed to the next workflow
| if [[ $OS_TYPE == Darwin ]]; then | ||
| brew install llvm@$VERSION | ||
| else | ||
| $MODE apt install lsb-release wget software-properties-common gnupg |
There was a problem hiding this comment.
If we use apt is it working on all Linux based OSs?
There was a problem hiding this comment.
yes, let's start here, with the common OSs to devs, and see if we need to add support to other OSs as well
|
IMO CI infrastructure should be aligned and up-to-date across all maintained branches (master and versions). This makes maintaining the CI much simpler as we practically have a single infra, and if something breaks we only need a single fix (with CPs) |
| san: addr | ||
| san: address | ||
| env: ubuntu-latest | ||
| rejson: 0 |
There was a problem hiding this comment.
Still needed? json sanitizer hiccup solved
| run: | | ||
| ${{ steps.mode.outputs.mode }} SANITIZER=${{ inputs.san }} BUILD_TLS=yes make install |
There was a problem hiding this comment.
| run: | | |
| ${{ steps.mode.outputs.mode }} SANITIZER=${{ inputs.san }} BUILD_TLS=yes make install | |
| env: | |
| BUILD_TLS: yes | |
| SANITIZER: ${{ input.san }} | |
| run: ${{ steps.mode.outputs.mode }} make install |
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin 2.8
git worktree add -d .worktree/backport-4726-to-2.8 origin/2.8
cd .worktree/backport-4726-to-2.8
git switch --create backport-4726-to-2.8
git cherry-pick -x 29d0b784048d5f8c00a6b7792664a8d5c87ba840 |
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin 2.6
git worktree add -d .worktree/backport-4726-to-2.6 origin/2.6
cd .worktree/backport-4726-to-2.6
git switch --create backport-4726-to-2.6
git cherry-pick -x 29d0b784048d5f8c00a6b7792664a8d5c87ba840 |
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin 2.10
git worktree add -d .worktree/backport-4726-to-2.10 origin/2.10
cd .worktree/backport-4726-to-2.10
git switch --create backport-4726-to-2.10
git cherry-pick -x 29d0b784048d5f8c00a6b7792664a8d5c87ba840 |
|
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin 8.0
git worktree add -d .worktree/backport-4726-to-8.0 origin/8.0
cd .worktree/backport-4726-to-8.0
git switch --create backport-4726-to-8.0
git cherry-pick -x 29d0b784048d5f8c00a6b7792664a8d5c87ba840 |
* wip * wip * wip * wip * delete * added get-redis input to sanitzier * removed no draft for sanitizer * added mode for llvm install * restored build redisjson * wip * after rebase * fixed typo * llvm_version * restored install boost * fixed? * set clang and llvm version * take llvm version from env * fixed build redisjson * don't run json on sanitizer * fixed task-test * removed flow-sanitizer * moved rust and llvm to test_deps. fixed llvm params order * fixed PR comments * remove unused * upload logs if canceled * tmp add test * also on coord * try explicitly set flags * 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 * added LD flag * trying the whole tests * delete event mirror * try a clean container * add -y * add curl to jammy * single tests for logs * add SAN to cmake defs * shared linker flags * fixed a typo * build redis with clang * Add cflags to redis for sanitizer * remove = * skip json in new json test, split phases in build redis (install after) * Switch position Build_tls and sanitizer * typo in sanitizer * run full test suite * Set sanitizer to run against latest redis with static libstdc++ * Run tests with json as well * removed jammy from PR event * bring back jammy * added jammy to merge queue and nightly * added test_config to merge queue * install LLVM only on sanitizer * added working directory * curl * remove curl from amazon linux 2023 * bring back install llvm * put rust in bashrc * add rest to path - another attempt * move rust to common installations --------- Co-authored-by: kei-nan <jonathan.keinan@redis.com> Co-authored-by: alon-reshef <alon.reshef@redis.com> Co-authored-by: alonre24 <alonreshef24@gmail.com>
Describe the changes in the pull request
This PR purges Readies from the sanitizer flow, allowing for an easier, less intrusive workflow by using the standard docker and dependency toolchain.
This PR unifies the flows for all test flows (test, coverage, sanitizer) to use
task-test.yml.This PR moves the llvm and rust installations to our common
.installfolder, where they should be, and removes them frombuild-rejsonscriptAs a temporary workaround, this PR also disables sanitizer with JSON tests, until a fix is submitted to RedisJSON repo
Also, we link statically to libstdc++ when we run sanitizer, since otherwise we crash in geometry tests otherwise. This is fine as long as we test sanitizer against redis 7.4. When we move to test against redis 8, we should link libstdc++ dynamically (as we do from now on).
Which issues this PR fixes
MOD-7453
Main objects this PR modified
task-test.yml
build-rejson