[CI/Build] Bump PyNvVideoCodec version - #47139
Conversation
Signed-off-by: Isotr0py <Isotr0py@outlook.com>
This comment was marked as resolved.
This comment was marked as resolved.
|
A release pipeline run is triggered at: https://buildkite.com/vllm/release-v2/builds/3338 |
Signed-off-by: Shengqi Chen <harry-chen@outlook.com>
|
@Harry-Chen Just seeing this in my morning time. pynvvideocodec 2.1.0 is known to have an issue which is why we had 2.0.4 as the set dependency. (I'm asking the team to better understand if it affects us here in vLLM or not). Can you tell me which architectures/versions of the wheels are required for the vLLM pipeline? I saw your comment in the original PR that the wheels for 2.0.4 didn't support the necessary configuration, but it wasn't clear to me which version(s) you need for aarch64? We can make sure going forward that necessary versions are being built in future releases of pynvvideocodec. |
|
@Harry-Chen I just asked and it sounds like we could publish another wheel for 2.0.4 if we can know the architectures required. |
Yes, if you can have the |
|
@Harry-Chen @brandonpelfrey Hi. Why doesn't PyNvVideoCodec==2.1.0 have wheels for cp313 and above? |
Oops. I think we still need to make it optional then. |
Signed-off-by: wang.yuqi <yuqi.wang@daocloud.io>
PLEASE FILL IN THE PR DESCRIPTION HERE ENSURING ALL CHECKLIST ITEMS (AT THE BOTTOM) HAVE BEEN CONSIDERED.
Purpose
Test Plan
Test Result
Essential Elements of an Effective PR Description Checklist
supported_models.mdandexamplesfor a new model.BEFORE SUBMITTING, PLEASE READ https://docs.vllm.ai/en/latest/contributing (anything written below this line will be removed by GitHub Actions)