Bug#1040056: [Pkg-opencl-devel] Bug#1040056: spirv-tools breaks spirv-llvm-translator-15 autopkgtest: exactly one input file must be specified.

2023-07-10 Thread Paul Gevers

Hi,

On 10-07-2023 11:30, Andreas Beckmann wrote:

Does this issue affect spirv-llvm-translator-16, too?
I tried to trigger the corresponding tests (which succeeded), but I'm 
not sure if it really tested the correct setup.


https://release.debian.org/britney/excuses.yaml.gz tells me that -16 was 
tested too and that it didn't fail (NEUTRAL; link to the log is in the 
excuses.yaml).


Paul


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1040056: spirv-tools breaks spirv-llvm-translator-15 autopkgtest: exactly one input file must be specified.

2023-07-10 Thread Sebastien Bacher

Hey Michel,

Sorry you are right there, unsure how I went to that conclusion but 
indeed what I wrote before was wrong


Cheers,
Sébastien

Le 10/07/2023 à 12:21, Michel Dänzer a écrit :

On 7/10/23 10:36, Sebastien Bacher wrote:

The issue needs to be fixed in piglit and there is a patch upstream, I've 
reported that as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039592

The spirv-llvm-translator build doesn't use piglit though, does it?



https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/821

However, 'spirv-as -h' still says:

'If no file is specified, [...] then the assembly text is read from standard 
input.'

So this does seem like a spirv-tools bug, and my piglit change is a workaround.






Bug#1040056: spirv-tools breaks spirv-llvm-translator-15 autopkgtest: exactly one input file must be specified.

2023-07-10 Thread Michel Dänzer
On 7/10/23 10:36, Sebastien Bacher wrote:
> The issue needs to be fixed in piglit and there is a patch upstream, I've 
> reported that as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039592

The spirv-llvm-translator build doesn't use piglit though, does it?


> https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/821

However, 'spirv-as -h' still says:

'If no file is specified, [...] then the assembly text is read from standard 
input.'

So this does seem like a spirv-tools bug, and my piglit change is a workaround.


-- 
Earthling Michel Dänzer|  https://redhat.com
Libre software enthusiast  | Mesa and Xwayland developer



Bug#1040056: [Pkg-opencl-devel] Bug#1040056: spirv-tools breaks spirv-llvm-translator-15 autopkgtest: exactly one input file must be specified.

2023-07-10 Thread Andreas Beckmann

Does this issue affect spirv-llvm-translator-16, too?
I tried to trigger the corresponding tests (which succeeded), but I'm 
not sure if it really tested the correct setup.


Andreas



Bug#1040056: spirv-tools breaks spirv-llvm-translator-15 autopkgtest: exactly one input file must be specified.

2023-07-10 Thread Sebastien Bacher
The issue needs to be fixed in piglit and there is a patch upstream, 
I've reported that as 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039592


https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/821



Bug#1040056: spirv-tools breaks spirv-llvm-translator-15 autopkgtest: exactly one input file must be specified.

2023-07-01 Thread Paul Gevers

Source: spirv-tools, spirv-llvm-translator-15
Control: found -1 spirv-tools/2023.3-1
Control: found -1 spirv-llvm-translator-15/15.0.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of spirv-tools the autopkgtest of 
spirv-llvm-translator-15 fails in testing when that autopkgtest is run 
with the binary packages of spirv-tools from unstable. It passes when 
run with only packages from testing. In tabular form:


   passfail
spirv-toolsfrom testing2023.3-1
spirv-llvm-translator-15 from testing15.0.0-2
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of spirv-tools to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=spirv-tools

https://ci.debian.net/data/autopkgtest/testing/amd64/s/spirv-llvm-translator-15/34967727/log.gz

 40s + sed -n -r /^Build/,/^$/s/.*llvm-([0-9]+)-dev.*/\1/p debian/control
 40s + LLVM_VERSION=15
 40s + cp -a . /tmp/autopkgtest-lxc.q8lw4m5c/downtmp/autopkgtest_tmp
 40s + cd /tmp/autopkgtest-lxc.q8lw4m5c/downtmp/autopkgtest_tmp
 40s + mkdir build
 40s + cd build
 40s + cmake -DLLVM_EXTERNAL_SPIRV_HEADERS_SOURCE_DIR=/usr/include 
-DLLVM_SPIRV_INCLUDE_TESTS=ON 
-DLLVM_EXTERNAL_LIT=/usr/lib/llvm-15/build/utils/lit/lit.py -Wno-dev ..
 40s -- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.1") 
40s -- Using SPIR-V Headers from

 40s   /usr/include
 40s -- The CXX compiler identification is GNU 12.3.0
 40s -- The C compiler identification is GNU 12.3.0
 40s -- Detecting CXX compiler ABI info
 40s -- Detecting CXX compiler ABI info - done
 40s -- Check for working CXX compiler: /usr/bin/c++ - skipped
 40s -- Detecting CXX compile features
 40s -- Detecting CXX compile features - done
 40s -- Detecting C compiler ABI info
 40s -- Detecting C compiler ABI info - done
 40s -- Check for working C compiler: /usr/bin/cc - skipped
 40s -- Detecting C compile features
 40s -- Detecting C compile features - done
 40s -- Performing Test HAVE_FFI_CALL
 40s -- Performing Test HAVE_FFI_CALL - Success
 40s -- Found FFI: /usr/lib/x86_64-linux-gnu/libffi.so   40s -- 
Performing Test Terminfo_LINKABLE

 40s -- Performing Test Terminfo_LINKABLE - Success
 40s -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so   40s -- 
Could NOT find ZLIB (missing: ZLIB_LIBRARY ZLIB_INCLUDE_DIR)  40s -- 
Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version 
"2.9.14")  41s -- Linker detection: GNU ld

 41s -- Performing Test C_SUPPORTS_FPIC
 41s -- Performing Test C_SUPPORTS_FPIC - Success
 41s -- Performing Test CXX_SUPPORTS_FPIC
 41s -- Performing Test CXX_SUPPORTS_FPIC - Success
 41s -- Building with -fPIC
 41s -- Performing Test C_SUPPORTS_FNO_SEMANTIC_INTERPOSITION
 41s -- Performing Test C_SUPPORTS_FNO_SEMANTIC_INTERPOSITION - Success
 41s -- Performing Test CXX_SUPPORTS_FNO_SEMANTIC_INTERPOSITION
 41s -- Performing Test CXX_SUPPORTS_FNO_SEMANTIC_INTERPOSITION - Success
 41s -- Performing Test SUPPORTS_FVISIBILITY_INLINES_HIDDEN_FLAG
 41s -- Performing Test SUPPORTS_FVISIBILITY_INLINES_HIDDEN_FLAG - Success
 41s -- Performing Test C_SUPPORTS_WERROR_DATE_TIME
 41s -- Performing Test C_SUPPORTS_WERROR_DATE_TIME - Success
 41s -- Performing Test CXX_SUPPORTS_WERROR_DATE_TIME
 41s -- Performing Test CXX_SUPPORTS_WERROR_DATE_TIME - Success
 41s -- Performing Test C_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW
 41s -- Performing Test C_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW - 
Failed

 41s -- Performing Test CXX_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW
 41s -- Performing Test CXX_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW 
- Failed

 41s -- Performing Test CXX_SUPPORTS_MISSING_FIELD_INITIALIZERS_FLAG
 42s -- Performing Test CXX_SUPPORTS_MISSING_FIELD_INITIALIZERS_FLAG - 
Success

 42s -- Performing Test C_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG
 42s -- Performing Test C_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG - Success
 42s -- Performing Test CXX_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG
 42s -- Performing Test CXX_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG - Success
 42s -- Performing Test C_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG
 42s -- Performing Test C_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG - Failed
 42s -- Performing Test CXX_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG
 42s -- Performing Test CXX_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG - Failed
 42s -- Performing Test CXX_SUPPORTS_CLASS_MEMACCESS_FLAG
 42s -- Performing Test CXX_SUPPORTS_CLASS_MEMACCESS_FLAG - Success
 42s -- Performing Test CXX_SUPPORTS_REDUNDANT_MOVE_FLAG
 42s