Skip to content

Skip OOM-related tests on incompatible platforms.#9386

Merged
yossigo merged 1 commit intoredis:unstablefrom
yossigo:skip-corrupt-dump-tests
Aug 18, 2021
Merged

Skip OOM-related tests on incompatible platforms.#9386
yossigo merged 1 commit intoredis:unstablefrom
yossigo:skip-corrupt-dump-tests

Conversation

@yossigo
Copy link
Collaborator

@yossigo yossigo commented Aug 18, 2021

We only run OOM related tests on x86_64 and aarch64, as jemalloc on other
platforms (notably s390x) may actually succeed very large allocations. As
a result the test may hang for a very long time at the cleanup phase,
iterating as many as 2^61 hash table slots.

We only run OOM related tests on x86_64 and aarch64, as jemalloc on other
platforms (notably s390x) may actually succeed very large allocations. As
a result the test may hang for a very long time at the cleanup phase,
iterating as many as 2^61 hash table slots.
@yossigo yossigo requested a review from oranagra August 18, 2021 12:02
@oranagra oranagra linked an issue Aug 18, 2021 that may be closed by this pull request
@yossigo yossigo merged commit 1d9c8d6 into redis:unstable Aug 18, 2021
@yossigo yossigo deleted the skip-corrupt-dump-tests branch August 18, 2021 13:00
JackieXie168 pushed a commit to JackieXie168/redis that referenced this pull request Sep 8, 2021
We only run OOM related tests on x86_64 and aarch64, as jemalloc on other
platforms (notably s390x) may actually succeed very large allocations. As
a result the test may hang for a very long time at the cleanup phase,
iterating as many as 2^61 hash table slots.
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.

[BUG] OOM in dictExpand on s390x architecture

2 participants