ci: fix the linux-leaks job
#4085
Merged
Conversation
This file contains hidden or 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
Cherry pick commit d3775de (Makefile: force -O0 when compiling with SANITIZE=leak, 2022-10-18), as otherwise the leak checker at GitHub Actions CI seems to fail with a false positive. [Backported to v2.37.0 for easier merging e.g. into Git for Windows] Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
dscho
force-pushed
the
fix-linux-leaks
branch
from
d952c6f to
b6afb3f
Compare
derrickstolee
approved these changes
Oct 28, 2022
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 28, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 28, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 28, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 28, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 28, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 28, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 28, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 28, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 28, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 28, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 28, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 28, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 28, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 31, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 31, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 31, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 31, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Oct 31, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 2, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Nov 2, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 3, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 3, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 3, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Nov 3, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Nov 3, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 3, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 3, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Nov 3, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Nov 3, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 3, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 3, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Nov 4, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 4, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 4, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 7, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Nov 8, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 9, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 9, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 9, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 10, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 10, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 12, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Nov 15, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 15, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 15, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 16, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
dscho
added a commit
that referenced
this pull request
Nov 16, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Nov 16, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Nov 17, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
git-for-windows-ci
pushed a commit
that referenced
this pull request
Nov 17, 2022
The CI builds have been seriously broken as of v2.38.1 by the constantly failing `linux-leaks` job. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The CI builds have been seriously broken as of v2.38.1 by the constantly failing
linux-leaksjob. Let's backport the work-around that has been applied to upstream Git (but that funnily has not been based directly on top of v2.38.1).