CI: Fix pathfinder CI infrastructure

@leofang

Great question. I think you've discovered a flaw in the current CI design... we weren't prepared to always fetch the pathfinder wheel from the main branch. So right now with the backport branch we do have two different sources...

As a bandaid, I can manually backport all changes in the pathfinder from the main branch. Later we can improve the CI design to fetch pathfinder from the main branch in the 12.9.x CI (just like how we fetch 12.9.x wheels from the backport branch in the main CI, but in the reversed direction). WDYT?

Originally posted by @leofang in #806 (comment)

Closed by #904. Not sure why GH did not close it automatically.

Ran into this and realized we need a proper fix before closing.

With #904 the two branches currently diverge in the way they fetch the pathfinder artifact:

12.9.x:

cuda-python/.github/workflows/test-wheel-linux.yml

Lines 133 to 149 in 2b6609f

    
                 - name: Download cuda-pathfinder build artifacts from main branch 
        
                   env: 
        
                     GH_TOKEN: ${{ secrets.GITHUB_TOKEN }} 
        
                   run: | 
        
                     MAIN_BRANCH="main" 
        
                     PATHFINDER_BASENAME="cuda-pathfinder-wheel" 
        
                     LATEST_MAIN_RUN_ID=$(gh run list -b ${MAIN_BRANCH} -L 1 -w "CI" -s completed -R NVIDIA/cuda-python --json databaseId | jq '.[]| .databaseId') 
        
                     if [[ "$LATEST_MAIN_RUN_ID" == "" ]]; then 
        
                       echo "LATEST_MAIN_RUN_ID not found!" 
        
                       exit 1 
        
                     fi 
        
                     gh run download $LATEST_MAIN_RUN_ID -p ${PATHFINDER_BASENAME} -R NVIDIA/cuda-python 
        
                     ls -al $PATHFINDER_BASENAME 
        
                     mkdir -p ./cuda_pathfinder 
        
                     mv $PATHFINDER_BASENAME/*.whl ./cuda_pathfinder/ 
        
                     rmdir $PATHFINDER_BASENAME

main:

cuda-python/.github/workflows/test-wheel-linux.yml

Lines 117 to 121 in 4a58adb

    
           - name: Download cuda-pathfinder build artifacts 
        
             uses: actions/download-artifact@70fc10c6e5e1ce46ad2ea6f2b72d43f7d47b13c3  # v8.0.0 
        
             with: 
        
               name: cuda-pathfinder-wheel 
        
               path: ./cuda_pathfinder

Because on main we did not add a proper logic in deciding "which branch am I on?" by the time we cut a v13.x backport branch when v14 is out this logic would fail.

We need to either fix this in the main branch, or figure out a new maintenance strategy before the next CUDA major comes (#1199).

I removed the P0 label because this is in the backlog. (I want to keep the P0, P1, P2 labels in sync with what we're actually doing.)

Closing as superseded by #1199, per leofang's 2026-03-05 comment — the residual here is bindings branching strategy, and #2675 is in flight against it.

The concrete 12.9.x vs main pathfinder fetch asymmetry has been recorded on #1199 so it survives this closure.

Navigation Menu

Repository navigation

CI: Fix pathfinder CI infrastructure #810

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

	- name: Download cuda-pathfinder build artifacts from main branch
	env:
	GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
	run: \|
	MAIN_BRANCH="main"
	PATHFINDER_BASENAME="cuda-pathfinder-wheel"
	LATEST_MAIN_RUN_ID=$(gh run list -b ${MAIN_BRANCH} -L 1 -w "CI" -s completed -R NVIDIA/cuda-python --json databaseId \| jq '.[]\| .databaseId')
	if [[ "$LATEST_MAIN_RUN_ID" == "" ]]; then
	echo "LATEST_MAIN_RUN_ID not found!"
	exit 1
	fi

	gh run download $LATEST_MAIN_RUN_ID -p ${PATHFINDER_BASENAME} -R NVIDIA/cuda-python
	ls -al $PATHFINDER_BASENAME
	mkdir -p ./cuda_pathfinder
	mv $PATHFINDER_BASENAME/*.whl ./cuda_pathfinder/
	rmdir $PATHFINDER_BASENAME

	- name: Download cuda-pathfinder build artifacts
	uses: actions/download-artifact@70fc10c6e5e1ce46ad2ea6f2b72d43f7d47b13c3 # v8.0.0
	with:
	name: cuda-pathfinder-wheel
	path: ./cuda_pathfinder

CI: Fix pathfinder CI infrastructure #810

Description

Activity

leofang commented on Aug 26, 2025

leofang commented on Mar 5, 2026

rwgk commented on Mar 17, 2026

rparolin commented on Aug 20, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions