From: Greg Hogan <code@greghogan.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: christopher@librehacker.com, 43779@debbugs.gnu.org,
Christopher Howard <christopher.howard@qlfiles.net>
Subject: bug#43779: tbb: test_global_control failure
Date: Fri, 9 Oct 2020 07:55:13 -0400 [thread overview]
Message-ID: <CA+3U0ZmQ9X9=oa95uEGZyS+Zbmx8ghfKa84c57y4tcPFoEkYKg@mail.gmail.com> (raw)
In-Reply-To: <875z7lvi40.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2143 bytes --]
I am also successfully building tbb-2020.3 and octave-5.2.0 locally. Is it
possible to retry the build on ci.guix.gnu.org?
I'm still puzzled why the 64-bit builds of tbb-2020.3 are missing from
ci.guix.gnu.org.
And previous versions of tbb have had mixed success building.
https://data.guix.gnu.org/repository/1/branch/master/package/tbb/output-history
But the logs for the old failed builds are missing.
https://ci.guix.gnu.org/log/jj0ym95spwggf519jmgkfzjy5vk28g3h-tbb-2020.1
https://ci.guix.gnu.org/log/nfxwyk82y38irsf75pshaklmfm6vnhsq-tbb-2020.0
On Wed, Oct 7, 2020 at 5:31 PM Ludovic Courtès <ludo@gnu.org> wrote:
> Hi,
>
> Greg Hogan <code@greghogan.com> skribis:
>
> > I don’t see any build failures on ci.guix.gnu.org <
> http://ci.guix.gnu.org/>, only two successes. Where is x86_64, should it
> not at least show as pending?
> >
> > Builds matching tbb-2020.3
> > ID Specification Completion time Job Name System Log
> > 3253827 guix-master 2 Oct 10:51 +0200
> tbb-2020.3.armhf-linux tbb-2020.3 armhf-linux
> > 3253435 guix-master 2 Oct 02:17 +0200
> tbb-2020.3.i686-linux tbb-2020.3 i686-linux
>
> Here’s the build log of a failure on x86_64:
>
> https://ci.guix.gnu.org/log/qc926v75q54k94mwgz6gn4s02sjgrr03-tbb-2020.3
>
> (You can build such URLs by appending the basename of the store file
> name to “https://ci.guix.gnu.org/log/”.)
>
> It ends like this:
>
> --8<---------------cut here---------------start------------->8---
> ./test_reader_writer_lock.exe
> done
> ./test_tbb_condition_variable.exe
> done
> ./test_intrusive_list.exe
> done
> ./test_concurrent_priority_queue.exe
> done
> ./test_task_priority.exe
> Known issue: priority effect is limited in case of blocking-style nesting
> make[1]: *** [../../build/Makefile.test:274: test_tbb_plain] Segmentation
> fault
> make[1]: Leaving directory
> '/tmp/guix-build-tbb-2020.3.drv-0/tbb-2020.3-checkout/build/guix_release'
> make: *** [Makefile:42: test] Error 2
> --8<---------------cut here---------------end--------------->8---
>
> Ludo’.
>
[-- Attachment #2: Type: text/html, Size: 3576 bytes --]
next prev parent reply other threads:[~2020-10-09 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-03 14:06 bug#43779: tbb: test_global_control failure Christopher Howard
2020-10-05 14:09 ` Ludovic Courtès
2020-10-05 15:36 ` Greg Hogan
2020-10-07 21:30 ` Ludovic Courtès
2020-10-09 11:55 ` Greg Hogan [this message]
2020-10-09 21:47 ` Ludovic Courtès
2024-03-07 16:33 ` Greg Hogan
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+3U0ZmQ9X9=oa95uEGZyS+Zbmx8ghfKa84c57y4tcPFoEkYKg@mail.gmail.com' \
--to=code@greghogan.com \
--cc=43779@debbugs.gnu.org \
--cc=christopher.howard@qlfiles.net \
--cc=christopher@librehacker.com \
--cc=ludo@gnu.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).