The following tests FAILED: 2 - spirv-tools-symbol-exports-SPIRV-Tools (Failed) 3 - spirv-tools-symbol-exports-SPIRV-Tools-shared (Failed) 4 - spirv-tools-symbol-exports-SPIRV-Tools-opt (Failed) 5 - spirv-tools-symbol-exports-SPIRV-Tools-link (Failed) ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-plasma-systemd_test_20180323-181400 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python2.7 (fallback) java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.7.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv dev-util/spirv-tools [ebuild N ] dev-util/spirv-tools-2018.2 ABI_X86="(64) -32 (-x32)"
Created attachment 525536 [details] emerge-info.txt
Created attachment 525538 [details] dev-util:spirv-tools-2018.2:20180326-142447.log
Created attachment 525540 [details] emerge-history.txt
Created attachment 525542 [details] environment
Created attachment 525544 [details] etc.portage.tbz2
Created attachment 525546 [details] LastTest.log
Created attachment 525548 [details] logs.tbz2
Created attachment 525550 [details] temp.tbz2
Created attachment 525552 [details] tests.tbz2
Upstream depends on Python 2.7 for the tests. Running them with 3.5/3.6 causes this failure. I am going to fix the ebuild to require 2.7 for tests. PR to come. Sarnex
Seems more complicated than that. The test checks that the symbols in the generated static libraries match some regular expression, and they may not depending on the compiler flags. More to come. Sarnex
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=024e9c947773e6e5800f126c8b8ce62dc21cf2a9 commit 024e9c947773e6e5800f126c8b8ce62dc21cf2a9 Author: Nick Sarnie <sarnex@gentoo.org> AuthorDate: 2018-04-23 02:23:41 +0000 Commit: Nick Sarnie <sarnex@gentoo.org> CommitDate: 2018-04-23 02:36:52 +0000 dev-util/spirv-tools: Restrict tests The tests go through all symbols in the generated libraries/executables, and check the symbol names against a hardcoded regular expression. If an unmatching symbol is found, the test fails. This is easily hit if a user sets a compiler flag that causes symbols to change, such as PIC Fixes: https://bugs.gentoo.org/651626 Package-Manager: Portage-2.3.31, Repoman-2.3.9 dev-util/spirv-tools/spirv-tools-2018.2-r1.ebuild | 3 +++ dev-util/spirv-tools/spirv-tools-9999.ebuild | 3 +++ 2 files changed, 6 insertions(+)
