unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Greg Hogan <code@greghogan.com>
Cc: christopher@librehacker.com, 43779@debbugs.gnu.org,
	Christopher Howard <christopher.howard@qlfiles.net>
Subject: bug#43779: tbb: test_global_control failure
Date: Wed, 07 Oct 2020 23:30:55 +0200	[thread overview]
Message-ID: <875z7lvi40.fsf@gnu.org> (raw)
In-Reply-To: <0B0D193F-886F-40AB-B181-07431015E539@greghogan.com> (Greg Hogan's message of "Mon, 5 Oct 2020 11:36:22 -0400")

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’.




  reply	other threads:[~2020-10-07 21:32 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 [this message]
2020-10-09 11:55       ` Greg Hogan
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=875z7lvi40.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=43779@debbugs.gnu.org \
    --cc=christopher.howard@qlfiles.net \
    --cc=christopher@librehacker.com \
    --cc=code@greghogan.com \
    /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).