Skip to content

MOD-7543 purge readies from sanitizer flow#4726

Merged
DvirDukhan merged 64 commits intomasterfrom
dvirdu_santizer
Dec 17, 2024
Merged

MOD-7543 purge readies from sanitizer flow#4726
DvirDukhan merged 64 commits intomasterfrom
dvirdu_santizer

Conversation

@DvirDukhan
Copy link

@DvirDukhan DvirDukhan commented Jun 9, 2024

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 .install folder, where they should be, and removes them from build-rejson script

As 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

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

@DvirDukhan DvirDukhan marked this pull request as ready for review August 8, 2024 08:58
@codecov
Copy link

codecov bot commented Aug 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.50%. Comparing base (ab3628d) to head (535acda).
Report is 1 commits behind head on master.

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.
📢 Have feedback on the report? Share it here.

@DvirDukhan DvirDukhan changed the title Dvirdu santizer MOD-7543 purge readies from sanitizer flow Aug 8, 2024
type: string
required: true
get-redis:
type: string
Copy link
Collaborator

Choose a reason for hiding this comment

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

This new parameter is not passed to the next workflow

Copy link
Author

Choose a reason for hiding this comment

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

removed flow

if [[ $OS_TYPE == Darwin ]]; then
brew install llvm@$VERSION
else
$MODE apt install lsb-release wget software-properties-common gnupg
Copy link
Collaborator

Choose a reason for hiding this comment

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

If we use apt is it working on all Linux based OSs?

Copy link
Author

Choose a reason for hiding this comment

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

yes, let's start here, with the common OSs to devs, and see if we need to add support to other OSs as well

@GuyAv46
Copy link
Collaborator

GuyAv46 commented Aug 8, 2024

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
Copy link
Collaborator

Choose a reason for hiding this comment

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

Still needed? json sanitizer hiccup solved

@DvirDukhan DvirDukhan enabled auto-merge November 17, 2024 17:09
alonre24
alonre24 previously approved these changes Nov 17, 2024
@DvirDukhan DvirDukhan added this pull request to the merge queue Nov 17, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Nov 17, 2024
@alonre24 alonre24 removed the request for review from oshadmi December 17, 2024 08:01
@alonre24 alonre24 disabled auto-merge December 17, 2024 08:02
@DvirDukhan DvirDukhan enabled auto-merge December 17, 2024 08:03
@alonre24 alonre24 requested a review from GuyAv46 December 17, 2024 08:14
Comment on lines +189 to +190
run: |
${{ steps.mode.outputs.mode }} SANITIZER=${{ inputs.san }} BUILD_TLS=yes make install
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
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

@DvirDukhan DvirDukhan added this pull request to the merge queue Dec 17, 2024
Merged via the queue into master with commit 29d0b78 Dec 17, 2024
@DvirDukhan DvirDukhan deleted the dvirdu_santizer branch December 17, 2024 09:49
@redisearch-backport-pull-request
Copy link
Contributor

Backport failed for 2.8, because it was unable to cherry-pick the commit(s).

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

@redisearch-backport-pull-request
Copy link
Contributor

Backport failed for 2.6, because it was unable to cherry-pick the commit(s).

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

@redisearch-backport-pull-request
Copy link
Contributor

Backport failed for 2.10, because it was unable to cherry-pick the commit(s).

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

@redisearch-backport-pull-request
Copy link
Contributor

Backport failed for 8.0, because it was unable to cherry-pick the commit(s).

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants