[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1068199: librocfft0: callback test failures on gfx900 and gfx1030



Package: librocfft0
Version: 5.7.1-1
Severity: normal
X-Debbugs-Cc: cgmb@slerp.xyz

Dear Maintainer,

The rocfft callback tests were passing with rocfft 5.5.1 on hip 5.2.3,
but began failing when hip was updated to 5.7.1. These failures are
specific to gfx900 and gfx1030 to gfx1036. The failures are not observed on
gfx803, gfx906, gfx1010, gfx1100 or gfx1101. This problem remains
unchanged by the update of rocfft to 5.7.1.

This is a sample of the failing test output [1]:

161s [ RUN      ] rocfft_UnitTest.default_load_callback_complex_single
161s clients/tests/default_callbacks_test.cpp:280: Failure
161s Expected equality of these values:
161s   rocfft_execute(plan, &in_ptr, &out_ptr, info)
161s     Which is: 1
161s   rocfft_status_success
161s     Which is: 0
161s
161s clients/tests/default_callbacks_test.cpp:310: Failure
161s Expected: (diff.l_inf) < (type_epsilon<Tbound>()), actual: 32.230823516845703 vs 3.75e-05
161s
161s [  FAILED  ] rocfft_UnitTest.default_load_callback_complex_single (349 ms)

It would be good to capture output with AMD_LOG_LEVEL=4 set in the
environment to view more information about the calls that are being made
to the HIP runtime.

Sincerely,
Cory Bloor

[1] https://ci.rocm.debian.net/data/autopkgtest/unstable/amd64+gfx1030/r/rocfft/9454/log.gz

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.9-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages librocfft0 depends on:
ii  libamdhip64-5  5.7.1-3
ii  libc6          2.37-15.1
ii  libgcc-s1      14-20240330-1
ii  libsqlite3-0   3.45.2-1
ii  libstdc++6     14-20240330-1

librocfft0 recommends no packages.

librocfft0 suggests no packages.

-- no debconf information


Reply to: