glibc: raise the test timeout so the huge page malloc test passes - #18396
Open
kgodara912 wants to merge 2 commits into
Open
glibc: raise the test timeout so the huge page malloc test passes#18396kgodara912 wants to merge 2 commits into
kgodara912 wants to merge 2 commits into
Conversation
malloc/tst-malloc-too-large-malloc-hugetlb2 was the only %check failure not covered by the expected failure list, so the whole test run was reported as failed. It is not a wrong result: the test is killed at the 20s default timeout while it needs about 35s, nearly all of it kernel time because the glibc.malloc.hugetlb=2 tunable exercises automatic huge pages. The plain and hugetlb1 variants of the same test pass. Set TIMEOUTFACTOR=10 so it runs to completion and actually asserts, rather than adding it to the tolerated failures. Verified locally: the only remaining failures are the ones already listed, plus two WSL specific misc/tst-preadvwritev2 failures that do not occur in the pipeline. Update the glibc NVRs in the toolchain and pkggen_core manifests for the release bump. The packages that BuildRequire glibc-static use a >= floor of 2.38-20, which 2.38-21 still satisfies, and the library itself is unchanged, so no dependent packages need rebuilding.
Author
microsoft-github-policy-service
Bot
added
Packaging
3.0-dev
check_static_glibc.py requires every spec with a glibc-static BuildRequires to name the current glibc release exactly, so the release bump has to be mirrored in all 16 consumers. Bump their releases and add changelog entries. libcap is also pinned in the toolchain and pkggen_core manifests, so update its NVRs there to match its own release bump.
microsoft-github-policy-service
Bot
added
the
specs-extended
kgodara912
marked this pull request as ready for review
August 12, 2026 05:26
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
malloc/tst-malloc-too-large-malloc-hugetlb2 was the only %check failure not covered by the expected failure list, so the whole test run was reported as failed. It is not a wrong result: the test is killed at the 20s default timeout while it needs about 35s, nearly all of it kernel time because the glibc.malloc.hugetlb=2 tunable exercises automatic huge pages. The plain and hugetlb1 variants of the same test pass.
Set TIMEOUTFACTOR=10 so it runs to completion and actually asserts, rather than adding it to the tolerated failures. Verified locally: the only remaining failures are the ones already listed, plus two WSL specific misc/tst-preadvwritev2 failures that do not occur in the pipeline.
Update the glibc NVRs in the toolchain and pkggen_core manifests for the release bump.