From: Andrey Savchenko <bircoph@altlinux.org> To: devel@lists.altlinux.org Subject: Re: [devel] sdcv-0.5.2-alt1: Sisyphus/x86_64 test rebuild failed Date: Sat, 22 Dec 2018 17:24:46 +0300 Message-ID: <20181222172446.649bdd6cefff0caeba05ce82@altlinux.org> (raw) In-Reply-To: <20181222063145.DC09F9A2F66@gyle.altlinux.org> [-- Attachment #1: Type: text/plain, Size: 1549 bytes --] On Sat, 22 Dec 2018 06:31:45 +0000 (UTC) ALT beekeeper wrote: > Package: sdcv-0.5.2-alt1 > Status: Sisyphus/x86_64 test rebuild failed > Cannot build this package. > Please investigate. > Excerpt from build log: [...] > The following tests FAILED: > 10 - t_datadir (Failed) > Errors while running CTest > error: Bad exit status from /usr/src/tmp/rpm-tmp.57609 (%check) > > RPM build errors: > Bad exit status from /usr/src/tmp/rpm-tmp.57609 (%check) > Command exited with non-zero status 1 > 10.66user 1.17system 0:18.86elapsed 62%CPU (0avgtext+0avgdata 176844maxresident)k > 0inputs+0outputs (0major+472874minor)pagefaults 0swaps > hsh-rebuild: rebuild of `sdcv-0.5.2-alt1.src.rpm' failed. > Command exited with non-zero status 1 Как мне извлечь из beehive содержимое $chroot/usr/src/RPM/BUILD/sdcv-0.5.2/BUILD/Testing/Temporary ? Там нужные для анализа проблемы логи. Локально проблема не воспроизводится. В сборочнице проблема не воспроизводится. Пересобираемость локально и в сборочнице 100%. Проблема с данным тестом может быть при недоступном на запись /tmp. Если на сборочнице снова закончилось место или отлетел /tmp по иной причине, то эта ошибка могла возникнуть. Best regards, Andrew Savchenko [-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2018-12-22 14:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-12-22 14:24 ` Andrey Savchenko [this message] 2018-12-22 15:22 ` Dmitry V. Levin 2018-12-22 18:07 ` Andrey Savchenko
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20181222172446.649bdd6cefff0caeba05ce82@altlinux.org \ --to=bircoph@altlinux.org \ --cc=devel@lists.altlinux.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux Team development discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \ devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru public-inbox-index devel Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.devel AGPL code for this site: git clone https://public-inbox.org/public-inbox.git