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