Upgrade KFP to 2.16.1 and increase pipeline timeout

[shruthis4]

Summary

This PR addresses two issues with the local pipeline test runner:

1. Upgrades KFP from 2.14.6 to 2.16.1 to fix compatibility with newer Docling images
2. Increases pipeline timeout from 15 to 30 minutes to accommodate VLM model downloads

Problem

The test-local-pipelines workflow was failing when using quay.io/aipcc/docling/sdk-cuda-ubi9:3.5.0-ea.2 with two errors:

Error 1: KFP Version Mismatch

ERROR: Could not find a version that satisfies the requirement kfp==2.14.6 (from versions: 2.16.1)
ERROR: No matching distribution found for kfp==2.14.6

The newer Docling CUDA image only provides KFP 2.16.1 in its Python environment.

Error 2: Timeout During Model Download

Error: The action 'Run local pipeline' has timed out after 15 minutes.

The VLM pipeline downloads SmolVLM and smoldocling models from HuggingFace, which includes multiple ONNX variants. These downloads were timing out at 15 minutes.

Changes

• .github/workflows/execute-kfp-localrunners.yml:
  • Updated KFP version from 2.14.6 to 2.16.1 (line 135)
  • Increased timeout from 15 to 30 minutes (line 149)
  • Minor whitespace cleanup

Testing

• Tested with quay.io/aipcc/docling/sdk-cuda-ubi9:3.5.0-ea.2
• Both docling-standard and docling-vlm pipelines complete successfully

Notes

The 30-minute timeout should be sufficient for VLM model downloads even with unauthenticated HuggingFace access. For faster downloads in production, consider setting HF_TOKEN for authenticated access.

[coderabbitai]

Warning

Review limit reached

@shruthis4, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 35 minutes and 38 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 5c533d0c-065e-4037-bbec-e1df29cedd0d

📥 Commits

Reviewing files that changed from the base of the PR and between 76564ea and 402baf8.

📒 Files selected for processing (1)

• .github/workflows/execute-kfp-localrunners.yml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[shruthis4]

Here is the successful pipeline run with quay.io/aipcc/docling/sdk-cuda-ubi9:3.5.0-ea.2
https://github.com/opendatahub-io/data-processing/actions/runs/27766617589