LFS 8.3 Glibc-2.28 make check fail 'stdlib/test-bz22786'
I am on Section 6.9 of the LFS book, My host OS is Ubuntu 18.04, When I ran make check I got errors as follow:
UNSUPPORTED: elf/tst-audit10
UNSUPPORTED: elf/tst-avx512
XPASS: elf/tst-protected1a
XPASS: elf/tst-protected1b
FAIL: inet/tst-idna_name_classify
UNSUPPORTED: math/test-double-libmvec-alias-avx512
UNSUPPORTED: math/test-double-libmvec-alias-avx512-main
UNSUPPORTED: math/test-double-libmvec-sincos-avx512
UNSUPPORTED: math/test-float-libmvec-alias-avx512
UNSUPPORTED: math/test-float-libmvec-alias-avx512-main
UNSUPPORTED: math/test-float-libmvec-sincosf-avx512
UNSUPPORTED: misc/tst-pkey
FAIL: misc/tst-ttyname
UNSUPPORTED: nptl/test-cond-printers
UNSUPPORTED: nptl/test-condattr-printers
UNSUPPORTED: nptl/test-mutex-printers
UNSUPPORTED: nptl/test-mutexattr-printers
UNSUPPORTED: nptl/test-rwlock-printers
UNSUPPORTED: nptl/test-rwlockattr-printers
UNSUPPORTED: posix/tst-sysconf-empty-chroot
UNSUPPORTED: resolv/tst-resolv-ai_idn
UNSUPPORTED: resolv/tst-resolv-ai_idn-latin1
FAIL: stdlib/test-bz22786
Summary of test results:
3 FAIL
5836 PASS
18 UNSUPPORTED
17 XFAIL
2 XPASS
make[1]: *** [Makefile:347: tests] Error 1
make[1]: Leaving directory '/sources/glibc-2.28'
make: *** [Makefile:9: check] Error 2
I want know the error stdlib/test-bz22786 is a harmless message or not?
glibc lfs
add a comment |
I am on Section 6.9 of the LFS book, My host OS is Ubuntu 18.04, When I ran make check I got errors as follow:
UNSUPPORTED: elf/tst-audit10
UNSUPPORTED: elf/tst-avx512
XPASS: elf/tst-protected1a
XPASS: elf/tst-protected1b
FAIL: inet/tst-idna_name_classify
UNSUPPORTED: math/test-double-libmvec-alias-avx512
UNSUPPORTED: math/test-double-libmvec-alias-avx512-main
UNSUPPORTED: math/test-double-libmvec-sincos-avx512
UNSUPPORTED: math/test-float-libmvec-alias-avx512
UNSUPPORTED: math/test-float-libmvec-alias-avx512-main
UNSUPPORTED: math/test-float-libmvec-sincosf-avx512
UNSUPPORTED: misc/tst-pkey
FAIL: misc/tst-ttyname
UNSUPPORTED: nptl/test-cond-printers
UNSUPPORTED: nptl/test-condattr-printers
UNSUPPORTED: nptl/test-mutex-printers
UNSUPPORTED: nptl/test-mutexattr-printers
UNSUPPORTED: nptl/test-rwlock-printers
UNSUPPORTED: nptl/test-rwlockattr-printers
UNSUPPORTED: posix/tst-sysconf-empty-chroot
UNSUPPORTED: resolv/tst-resolv-ai_idn
UNSUPPORTED: resolv/tst-resolv-ai_idn-latin1
FAIL: stdlib/test-bz22786
Summary of test results:
3 FAIL
5836 PASS
18 UNSUPPORTED
17 XFAIL
2 XPASS
make[1]: *** [Makefile:347: tests] Error 1
make[1]: Leaving directory '/sources/glibc-2.28'
make: *** [Makefile:9: check] Error 2
I want know the error stdlib/test-bz22786 is a harmless message or not?
glibc lfs
add a comment |
I am on Section 6.9 of the LFS book, My host OS is Ubuntu 18.04, When I ran make check I got errors as follow:
UNSUPPORTED: elf/tst-audit10
UNSUPPORTED: elf/tst-avx512
XPASS: elf/tst-protected1a
XPASS: elf/tst-protected1b
FAIL: inet/tst-idna_name_classify
UNSUPPORTED: math/test-double-libmvec-alias-avx512
UNSUPPORTED: math/test-double-libmvec-alias-avx512-main
UNSUPPORTED: math/test-double-libmvec-sincos-avx512
UNSUPPORTED: math/test-float-libmvec-alias-avx512
UNSUPPORTED: math/test-float-libmvec-alias-avx512-main
UNSUPPORTED: math/test-float-libmvec-sincosf-avx512
UNSUPPORTED: misc/tst-pkey
FAIL: misc/tst-ttyname
UNSUPPORTED: nptl/test-cond-printers
UNSUPPORTED: nptl/test-condattr-printers
UNSUPPORTED: nptl/test-mutex-printers
UNSUPPORTED: nptl/test-mutexattr-printers
UNSUPPORTED: nptl/test-rwlock-printers
UNSUPPORTED: nptl/test-rwlockattr-printers
UNSUPPORTED: posix/tst-sysconf-empty-chroot
UNSUPPORTED: resolv/tst-resolv-ai_idn
UNSUPPORTED: resolv/tst-resolv-ai_idn-latin1
FAIL: stdlib/test-bz22786
Summary of test results:
3 FAIL
5836 PASS
18 UNSUPPORTED
17 XFAIL
2 XPASS
make[1]: *** [Makefile:347: tests] Error 1
make[1]: Leaving directory '/sources/glibc-2.28'
make: *** [Makefile:9: check] Error 2
I want know the error stdlib/test-bz22786 is a harmless message or not?
glibc lfs
I am on Section 6.9 of the LFS book, My host OS is Ubuntu 18.04, When I ran make check I got errors as follow:
UNSUPPORTED: elf/tst-audit10
UNSUPPORTED: elf/tst-avx512
XPASS: elf/tst-protected1a
XPASS: elf/tst-protected1b
FAIL: inet/tst-idna_name_classify
UNSUPPORTED: math/test-double-libmvec-alias-avx512
UNSUPPORTED: math/test-double-libmvec-alias-avx512-main
UNSUPPORTED: math/test-double-libmvec-sincos-avx512
UNSUPPORTED: math/test-float-libmvec-alias-avx512
UNSUPPORTED: math/test-float-libmvec-alias-avx512-main
UNSUPPORTED: math/test-float-libmvec-sincosf-avx512
UNSUPPORTED: misc/tst-pkey
FAIL: misc/tst-ttyname
UNSUPPORTED: nptl/test-cond-printers
UNSUPPORTED: nptl/test-condattr-printers
UNSUPPORTED: nptl/test-mutex-printers
UNSUPPORTED: nptl/test-mutexattr-printers
UNSUPPORTED: nptl/test-rwlock-printers
UNSUPPORTED: nptl/test-rwlockattr-printers
UNSUPPORTED: posix/tst-sysconf-empty-chroot
UNSUPPORTED: resolv/tst-resolv-ai_idn
UNSUPPORTED: resolv/tst-resolv-ai_idn-latin1
FAIL: stdlib/test-bz22786
Summary of test results:
3 FAIL
5836 PASS
18 UNSUPPORTED
17 XFAIL
2 XPASS
make[1]: *** [Makefile:347: tests] Error 1
make[1]: Leaving directory '/sources/glibc-2.28'
make: *** [Makefile:9: check] Error 2
I want know the error stdlib/test-bz22786 is a harmless message or not?
glibc lfs
glibc lfs
edited Nov 18 '18 at 7:25
zhiyong.li
asked Nov 13 '18 at 10:03
zhiyong.lizhiyong.li
62
62
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The old version of stdlib/test-bz22786 needed more than 2 GiB of RAM to complete successfully. If your system does not have that much RAM and uses swap space instead, the test will execute very slowly and eventually time out, leading to the test failure you see.
This is fixed on the release/2.28/master upstream branch, by backporting this upstream commit which uses alias mappings for memory compression. The backport needs some further patches, which are also on the branch. It's usually a good idea to track the release branch (except that a commit broke malloc earlier this week, so perhaps now is not a good time to start).
Thanks for paying attention to glibc test results.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53278450%2flfs-8-3-glibc-2-28-make-check-fail-stdlib-test-bz22786%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The old version of stdlib/test-bz22786 needed more than 2 GiB of RAM to complete successfully. If your system does not have that much RAM and uses swap space instead, the test will execute very slowly and eventually time out, leading to the test failure you see.
This is fixed on the release/2.28/master upstream branch, by backporting this upstream commit which uses alias mappings for memory compression. The backport needs some further patches, which are also on the branch. It's usually a good idea to track the release branch (except that a commit broke malloc earlier this week, so perhaps now is not a good time to start).
Thanks for paying attention to glibc test results.
add a comment |
The old version of stdlib/test-bz22786 needed more than 2 GiB of RAM to complete successfully. If your system does not have that much RAM and uses swap space instead, the test will execute very slowly and eventually time out, leading to the test failure you see.
This is fixed on the release/2.28/master upstream branch, by backporting this upstream commit which uses alias mappings for memory compression. The backport needs some further patches, which are also on the branch. It's usually a good idea to track the release branch (except that a commit broke malloc earlier this week, so perhaps now is not a good time to start).
Thanks for paying attention to glibc test results.
add a comment |
The old version of stdlib/test-bz22786 needed more than 2 GiB of RAM to complete successfully. If your system does not have that much RAM and uses swap space instead, the test will execute very slowly and eventually time out, leading to the test failure you see.
This is fixed on the release/2.28/master upstream branch, by backporting this upstream commit which uses alias mappings for memory compression. The backport needs some further patches, which are also on the branch. It's usually a good idea to track the release branch (except that a commit broke malloc earlier this week, so perhaps now is not a good time to start).
Thanks for paying attention to glibc test results.
The old version of stdlib/test-bz22786 needed more than 2 GiB of RAM to complete successfully. If your system does not have that much RAM and uses swap space instead, the test will execute very slowly and eventually time out, leading to the test failure you see.
This is fixed on the release/2.28/master upstream branch, by backporting this upstream commit which uses alias mappings for memory compression. The backport needs some further patches, which are also on the branch. It's usually a good idea to track the release branch (except that a commit broke malloc earlier this week, so perhaps now is not a good time to start).
Thanks for paying attention to glibc test results.
answered Nov 22 '18 at 21:14
Florian WeimerFlorian Weimer
15.5k31044
15.5k31044
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53278450%2flfs-8-3-glibc-2-28-make-check-fail-stdlib-test-bz22786%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown