Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
media-libs/OneVPL-2023.4.0 Tests fail... and then they don't
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Multimedia
View previous topic :: View next topic  
Author Message
Zeault
n00b
n00b


Joined: 03 Aug 2019
Posts: 22
Location: New England, United States

PostPosted: Fri Jan 12, 2024 12:16 pm    Post subject: media-libs/OneVPL-2023.4.0 Tests fail... and then they don't Reply with quote

I have an Intel integrated GPU and I've used ffmpeg built with use flag qsv. Ffmpeg 5 has depended on media-libs/intel-mediasdk but now with ffmpeg >6 that dependency has changed to oneVPL which is still keyworded ~amd64. I want to upgrade to ffmpeg 6 so I applied the keyword. I also have the habit of enabling the test phase for keyworded packages. With these settings my world update failed. I ran emerge --ask --oneshot oneVPL and it builds successfully but fails on the test phase.

These are the use flags I built it with:
Code:
[ebuild  N    ~] media-libs/oneVPL-2023.4.0  USE="X dri drm test vaapi -examples -experimental -tools -wayland" ABI_X86="(64) -32 (-x32)"


And these are the specific tests that fail:
Code:
181 - Dispatcher_LowLatency.Invalid_SingleConfig_MissingProp (Failed)
182 - Dispatcher_LowLatency.Invalid_SingleConfig_OverwriteProp (Failed)
183 - Dispatcher_LowLatency.Invalid_SingleConfig_WrongValue (Failed)
184 - Dispatcher_LowLatency.ValidPropsEnable_MultiConfig (Failed)
185 - Dispatcher_LowLatency.Invalid_MultiConfig_MissingProp (Failed)
186 - Dispatcher_LowLatency.Invalid_MultiConfig_OverwriteProp (Failed)
187 - Dispatcher_LowLatency.Invalid_MultiConfig_WrongValue (Failed)
Errors while running CTest
Output from these tests are in: /var/tmp/portage/media-libs/oneVPL-2023.4.0/work/libvpl-2023.4.0_build-abi_x86_64.amd64/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.


I followed the advice and reran the tests with the suggested switches:
Code:
cd /var/tmp/portage/media-libs/oneVPL-2023.4.0/work/libvpl-2023.4.0_build-abi_x86_64.amd64/
ctest --rerun-failed --output-on-failure


But then all the tests pass!

Code:
Test project /var/tmp/portage/media-libs/oneVPL-2023.4.0/work/libvpl-2023.4.0_build-abi_x86_64.amd64
    Start 181: Dispatcher_LowLatency.Invalid_SingleConfig_MissingProp
1/7 Test #181: Dispatcher_LowLatency.Invalid_SingleConfig_MissingProp .....   Passed    0.01 sec
    Start 182: Dispatcher_LowLatency.Invalid_SingleConfig_OverwriteProp
2/7 Test #182: Dispatcher_LowLatency.Invalid_SingleConfig_OverwriteProp ...   Passed    0.01 sec
    Start 183: Dispatcher_LowLatency.Invalid_SingleConfig_WrongValue
3/7 Test #183: Dispatcher_LowLatency.Invalid_SingleConfig_WrongValue ......   Passed    0.01 sec
    Start 184: Dispatcher_LowLatency.ValidPropsEnable_MultiConfig
4/7 Test #184: Dispatcher_LowLatency.ValidPropsEnable_MultiConfig .........   Passed    0.01 sec
    Start 185: Dispatcher_LowLatency.Invalid_MultiConfig_MissingProp
5/7 Test #185: Dispatcher_LowLatency.Invalid_MultiConfig_MissingProp ......   Passed    0.01 sec
    Start 186: Dispatcher_LowLatency.Invalid_MultiConfig_OverwriteProp
6/7 Test #186: Dispatcher_LowLatency.Invalid_MultiConfig_OverwriteProp ....   Passed    0.01 sec
    Start 187: Dispatcher_LowLatency.Invalid_MultiConfig_WrongValue
7/7 Test #187: Dispatcher_LowLatency.Invalid_MultiConfig_WrongValue .......   Passed    0.01 sec

100% tests passed, 0 tests failed out of 7

Total Test time (real) =   0.06 sec


I have enjoyed the freedom to choose and experiment that Gentoo provides me. I have done A LOT of odd experimentation with this particular system over the years so instead of posting a bug I kind of just assume that the problem is my fault for changing something. That said, I have always been impressed with the robustness of Gentoo packages and their ability to tolerate so many different configurations. This would be the first time I have really encountered an issue like this. Does anyone here on the forums have some suggestions for next troubleshooting steps?

I tried checking out that log file:
Code:
cd /var/tmp/portage/media-libs/oneVPL-2023.4.0/work/libvpl-2023.4.0_build-abi_x86_64.amd64/Testing/Temporary/
grep -C8 FAILED LastTest.log


The tests are having trouble opening a log file, and then writing to it.
Code:
Note: Google Test filter = Dispatcher_LowLatency.Invalid_SingleConfig_MissingProp
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from Dispatcher_LowLatency
[ RUN      ] Dispatcher_LowLatency.Invalid_SingleConfig_MissingProp
Info: CheckOutputLog(true) -- string message:  low latency mode disabled
/var/tmp/portage/media-libs/oneVPL-2023.4.0/work/libvpl-2023.4.0/libvpl/test/unit/src/dispatcher_util.cpp:82: Failure
Expected: (logPos) != (std::string::npos), actual: 18446744073709551615 vs 18446744073709551615
[  FAILED  ] Dispatcher_LowLatency.Invalid_SingleConfig_MissingProp (10 ms)
[----------] 1 test from Dispatcher_LowLatency (10 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (10 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] Dispatcher_LowLatency.Invalid_SingleConfig_MissingProp

 1 FAILED TEST
<end of output>
Test time =   0.02 sec
----------------------------------------------------------
Test Failed.
"Dispatcher_LowLatency.Invalid_SingleConfig_MissingProp" end time: Jan 12 06:40 EST
"Dispatcher_LowLatency.Invalid_SingleConfig_MissingProp" time elapsed: 00:00:00
----------------------------------------------------------

--
Note: Google Test filter = Dispatcher_LowLatency.Invalid_SingleConfig_OverwriteProp
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from Dispatcher_LowLatency
[ RUN      ] Dispatcher_LowLatency.Invalid_SingleConfig_OverwriteProp
Error: failed to open log file utestLogFile_vpl.txt
/var/tmp/portage/media-libs/oneVPL-2023.4.0/work/libvpl-2023.4.0/libvpl/test/unit/src/dispatcher_util.cpp:60: Failure
Failed
[  FAILED  ] Dispatcher_LowLatency.Invalid_SingleConfig_OverwriteProp (8 ms)
[----------] 1 test from Dispatcher_LowLatency (8 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (8 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] Dispatcher_LowLatency.Invalid_SingleConfig_OverwriteProp

 1 FAILED TEST
<end of output>
Test time =   0.02 sec
----------------------------------------------------------
Test Failed.
"Dispatcher_LowLatency.Invalid_SingleConfig_OverwriteProp" end time: Jan 12 06:40 EST
"Dispatcher_LowLatency.Invalid_SingleConfig_OverwriteProp" time elapsed: 00:00:00
----------------------------------------------------------

--
Note: Google Test filter = Dispatcher_LowLatency.Invalid_SingleConfig_WrongValue
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from Dispatcher_LowLatency
[ RUN      ] Dispatcher_LowLatency.Invalid_SingleConfig_WrongValue
Error: failed to open log file utestLogFile_vpl.txt
/var/tmp/portage/media-libs/oneVPL-2023.4.0/work/libvpl-2023.4.0/libvpl/test/unit/src/dispatcher_util.cpp:60: Failure
Failed
[  FAILED  ] Dispatcher_LowLatency.Invalid_SingleConfig_WrongValue (5 ms)
[----------] 1 test from Dispatcher_LowLatency (5 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (5 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] Dispatcher_LowLatency.Invalid_SingleConfig_WrongValue

 1 FAILED TEST
<end of output>
Test time =   0.02 sec
----------------------------------------------------------
Test Failed.
"Dispatcher_LowLatency.Invalid_SingleConfig_WrongValue" end time: Jan 12 06:40 EST
"Dispatcher_LowLatency.Invalid_SingleConfig_WrongValue" time elapsed: 00:00:00
----------------------------------------------------------

--
Note: Google Test filter = Dispatcher_LowLatency.ValidPropsEnable_MultiConfig
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from Dispatcher_LowLatency
[ RUN      ] Dispatcher_LowLatency.ValidPropsEnable_MultiConfig
Error: failed to open log file utestLogFile_vpl.txt
/var/tmp/portage/media-libs/oneVPL-2023.4.0/work/libvpl-2023.4.0/libvpl/test/unit/src/dispatcher_util.cpp:60: Failure
Failed
[  FAILED  ] Dispatcher_LowLatency.ValidPropsEnable_MultiConfig (3 ms)
[----------] 1 test from Dispatcher_LowLatency (3 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (3 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] Dispatcher_LowLatency.ValidPropsEnable_MultiConfig

 1 FAILED TEST
<end of output>
Test time =   0.01 sec
----------------------------------------------------------
Test Failed.
"Dispatcher_LowLatency.ValidPropsEnable_MultiConfig" end time: Jan 12 06:40 EST
"Dispatcher_LowLatency.ValidPropsEnable_MultiConfig" time elapsed: 00:00:00
----------------------------------------------------------

--
Note: Google Test filter = Dispatcher_LowLatency.Invalid_MultiConfig_MissingProp
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from Dispatcher_LowLatency
[ RUN      ] Dispatcher_LowLatency.Invalid_MultiConfig_MissingProp
Info: CheckOutputLog(true) -- string message:  low latency mode disabled
/var/tmp/portage/media-libs/oneVPL-2023.4.0/work/libvpl-2023.4.0/libvpl/test/unit/src/dispatcher_util.cpp:82: Failure
Expected: (logPos) != (std::string::npos), actual: 18446744073709551615 vs 18446744073709551615
[  FAILED  ] Dispatcher_LowLatency.Invalid_MultiConfig_MissingProp (5 ms)
[----------] 1 test from Dispatcher_LowLatency (5 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (5 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] Dispatcher_LowLatency.Invalid_MultiConfig_MissingProp

 1 FAILED TEST
<end of output>
Test time =   0.01 sec
----------------------------------------------------------
Test Failed.
"Dispatcher_LowLatency.Invalid_MultiConfig_MissingProp" end time: Jan 12 06:40 EST
"Dispatcher_LowLatency.Invalid_MultiConfig_MissingProp" time elapsed: 00:00:00
----------------------------------------------------------

--
Note: Google Test filter = Dispatcher_LowLatency.Invalid_MultiConfig_OverwriteProp
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from Dispatcher_LowLatency
[ RUN      ] Dispatcher_LowLatency.Invalid_MultiConfig_OverwriteProp
Info: CheckOutputLog(true) -- string message:  low latency mode disabled
/var/tmp/portage/media-libs/oneVPL-2023.4.0/work/libvpl-2023.4.0/libvpl/test/unit/src/dispatcher_util.cpp:82: Failure
Expected: (logPos) != (std::string::npos), actual: 18446744073709551615 vs 18446744073709551615
[  FAILED  ] Dispatcher_LowLatency.Invalid_MultiConfig_OverwriteProp (5 ms)
[----------] 1 test from Dispatcher_LowLatency (5 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (5 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] Dispatcher_LowLatency.Invalid_MultiConfig_OverwriteProp

 1 FAILED TEST
<end of output>
Test time =   0.01 sec
----------------------------------------------------------
Test Failed.
"Dispatcher_LowLatency.Invalid_MultiConfig_OverwriteProp" end time: Jan 12 06:40 EST
"Dispatcher_LowLatency.Invalid_MultiConfig_OverwriteProp" time elapsed: 00:00:00
----------------------------------------------------------

--
Note: Google Test filter = Dispatcher_LowLatency.Invalid_MultiConfig_WrongValue
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from Dispatcher_LowLatency
[ RUN      ] Dispatcher_LowLatency.Invalid_MultiConfig_WrongValue
Error: failed to open log file utestLogFile_vpl.txt
/var/tmp/portage/media-libs/oneVPL-2023.4.0/work/libvpl-2023.4.0/libvpl/test/unit/src/dispatcher_util.cpp:60: Failure
Failed
[  FAILED  ] Dispatcher_LowLatency.Invalid_MultiConfig_WrongValue (5 ms)
[----------] 1 test from Dispatcher_LowLatency (5 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (5 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] Dispatcher_LowLatency.Invalid_MultiConfig_WrongValue

 1 FAILED TEST
<end of output>
Test time =   0.02 sec
----------------------------------------------------------
Test Failed.
"Dispatcher_LowLatency.Invalid_MultiConfig_WrongValue" end time: Jan 12 06:40 EST
"Dispatcher_LowLatency.Invalid_MultiConfig_WrongValue" time elapsed: 00:00:00
----------------------------------------------------------


Finally, here is my make.conf:
Code:
# make.conf

# New Common Flags
COMMON_FLAGS = "-march=broadwell -mabm -madx -maes -mavx -mavx2 -mbmi -mbmi2 -mcx16 -mf16c -mfma \
-mfsgsbase -mfxsr -mhle -mlzcnt -mmmx -mmovbe -mpclmul -mpopcnt -mprfchw -mrdrnd \
-mrdseed -mrtm -msahf -msse -msse2 -msse3 -msse4.1 -msse4.2 -mssse3 -mxsave -mxsaveopt \
--param=l1-cache-line-size=64 --param=l1-cache-size=32 --param=l2-cache-size=3072
-mtune=broadwell -O2 -pipe"

# Old Common Flags
#COMMON_FLAGS="-march=native -mtune=native -O2 -pipe"

CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"

# NOTE: This stage was built with the bindist Use flag enabled
PORTDIR="/var/db/repos/gentoo"
DISTDIR="/var/cache/distfiles"
PKGDIR="/var/cache/binpkgs"

# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C

# Options passed to make during ebuild/emerge
MAKEOPTS="-j4"

# Mirros for downloading source code
GENTOO_MIRRORS="https://gentoo.osuosl.org/ ftp://ftp.ussg.iu.edu/pub/linux/gentoo https://gentoo.ussg.indiana.edu/"

# USE and related variables
CPU_FLAGS_X86="aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3"
INPUT_DEVICES="libinput"
VIDEO_CARDS="intel i965"
CURL_SSL="openssl"
L10N="en en-US"

USE="   acpi upower alsa pulseaudio -systemd gnutls \
   X dbus qt qt5 gtk vaapi colord \
   icu policykit elogind libnotify startup-notification networkmanager \
   exif tiff jpeg png gif opengl \
   ffmpeg gstreamer \
   odf pdf epub raw
"

FEATURES="userfetch userpriv usersandbox"
PORTAGE_SCHEDULING_POLICY="idle"

# Mike Gilbert <floppym@gentoo.org> (2022-08-31)
# Avoid removing merged-usr symlinks.
UNINSTALL_IGNORE="${UNINSTALL_IGNORE} /bin /lib /lib32 /lib64 /libx32 /sbin /usr/sbin"
UNINSTALL_IGNORE="${UNINSTALL_IGNORE} /usr/lib/modules/*"
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 21637

PostPosted: Fri Jan 12, 2024 3:48 pm    Post subject: Reply with quote

Portage normally runs as much of the build as it can under an unprivileged user. When you tried rerunning the test by hand, did you run it as the unprivileged user or as root? Since the issue is failure to open a file, it is plausible that this is a permissions issue, and when the test runs as root, it has permissions, but when it runs unprivileged, it lacks them.
Back to top
View user's profile Send private message
Zeault
n00b
n00b


Joined: 03 Aug 2019
Posts: 22
Location: New England, United States

PostPosted: Mon Jan 15, 2024 4:51 am    Post subject: Reply with quote

When the test succeeded I was running them as root. I tried disabling the 'drop privileges' feature of portage and building it again
Code:
FEATURES="-userpriv -usersandbox" emerge --ask --oneshot media-libs/oneVPL

but this had no effect on the outcome.

I am now trying to read the source code to see where the log file is supposed to live.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Multimedia All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum