Skip to content

Update video benchmark path - #2355

Open
meatybobby wants to merge 1 commit into
mainfrom
bobchen/video_benchmark_path
Open

Update video benchmark path#2355
meatybobby wants to merge 1 commit into
mainfrom
bobchen/video_benchmark_path

Conversation

@meatybobby

Copy link
Copy Markdown
Contributor

Description

Usage

# Add snippet demonstrating usage

Checklist

  • I am familiar with the Contributing Guide.
  • New or Existing tests cover these changes.
  • The documentation is up to date with these changes.

@meatybobby
meatybobby requested a review from a team as a code owner August 28, 2026 17:59
@meatybobby
meatybobby requested review from oyilmaz-nvidia and removed request for a team August 28, 2026 17:59
@copy-pr-bot

copy-pr-bot Bot commented Aug 28, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@greptile-apps

greptile-apps Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Updates the canonical benchmark configuration to load the sample video dataset from its OpenVid-1M subdirectory.

  • Changes the videos MP4 path from {datasets_path}/sample4k to {datasets_path}/openvid-1m/sample4k.

Confidence Score: 5/5

The PR appears safe to merge, with no concrete blocking or non-blocking issue identified.

The configuration-only change consistently redirects all consumers of the shared videos dataset, and no repository evidence contradicts the new directory layout.

Important Files Changed

Filename Overview
benchmarking/benchmarks.yaml Updates the shared video benchmark dataset path; no actionable defect is established by the repository context.

Reviews (1): Last reviewed commit: "Update video benchmark path" | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant