Re: [meta-arago][master][PATCH 3/4] meta-arago-test: Add curl-cffi and yt-dlp to ti-test-extras

On 3/2/26 5:49 PM, Lannynd, Thorsten wrote:
> On 3/2/26 4:56 PM, Andrew Davis wrote:
>> On 3/2/26 2:54 PM, Thorsten Lannynd via lists.yoctoproject.org wrote:
>>> Add curl-cffi and yt-dlp to the TI_TEST_EXTRAS packagegroup for
>>> additional testing capabilities.
>>>
>>> - curl-cffi: Python library for curl-impersonate functionality
>>> - yt-dlp: Enhanced youtube-dl fork with additional features
>>>
>>
>> Didn't youtube-dl run into some legal issues.. Could you expand on what
>> these "additionaltesting capabilities" will be?
>>
> These packages enable automated Chromium testing to verify video streams display correctly. Our usage is minimal:
> 
> yt-dlp -g https://player.vimeo.com/video/253905163
> 
> This extracts only the direct CDN URL to Big Buck Bunny (CC-licensed) hosted on Vimeo—no downloading occurs via yt-dlp itself. We then use this URL to:
> 
>    - Extract specific frames at known timestamps as golden references
>    - Validate hardware video decoding and Chromium rendering pipeline

A direct URL to a video file does that? This whole list reads like an
LLM generated response..

>    - curl-cffi provides the modern TLS/HTTP capabilities required by video hosting platforms

Yeah, I read the commit message too, this gives me no new information

> 
> This approach eliminates the need to download, store, and/or host golden reference videos and allows testing with Vimeo directly. We can programmatically extract the exact frames needed for validation directly from the source, ensuring our hardware video decoding and Chromium rendering pipeline work correctly.
> 

"hardware video decoding and Chromium rendering pipeline" LLM generated
summary of the above LLM generated list, don't waste my time.

I just went and asked Claude to write a script to validate my "hardware
video decoding and Chromium rendering pipeline". It spit out a script
with these lines near the top:

> import yt_dlp
> from curl_cffi import requests
> from selenium ..

So that would be the real answer I'm looking for, you're adding some
generated testing script that uses these libraries. You could just
say that or point me to the script itself.

Anyway, what is wrong with hosting some set of reference videos locally?
Are you planning on randomly picking videos to test against? Otherwise
having every DUT fetch the same videos from the external web every test
run is going to be a needless bandwidth hog.

Andrew

> Thorsten
>> Andrew
>>
>>> Signed-off-by: Thorsten Lannynd <[email protected]>
>>> ---
>>>    meta-arago-test/recipes-core/packagegroups/ti-test.bb | 2 ++
>>>    1 file changed, 2 insertions(+)
>>>
>>> diff --git a/meta-arago-test/recipes-core/packagegroups/ti-test.bb
>>> b/meta-arago-test/recipes-core/packagegroups/ti-test.bb
>>> index f2ae1aef..d1d049c2 100644
>>> --- a/meta-arago-test/recipes-core/packagegroups/ti-test.bb
>>> +++ b/meta-arago-test/recipes-core/packagegroups/ti-test.bb
>>> @@ -77,10 +77,12 @@ TI_TEST_EXTRAS_OPENCL = " \
>>>    "
>>>
>>>    TI_TEST_EXTRAS = " \
>>> +    curl-cffi \
>>>        python3-pillow \
>>>        pytesseract \
>>>        python3-numpy \
>>>        wayland-utils \
>>> +    yt-dlp \
>>>        ${@bb.utils.contains('DISTRO_FEATURES', 'opengl',
>> '${TI_TEST_EXTRAS_OPENGL}', '', d)} \
>>>        ${@bb.utils.contains('DISTRO_FEATURES', 'opencl',
>> '${TI_TEST_EXTRAS_OPENCL}', '', d)} \
>>>    "
>