Pva Build Test
NVIDIAOfficialCreated by Venkat BalanDistributed by NVIDIA
- Skill
- Workflow
- Software development
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The pva-build-test skill provides a structured procedure to build and verify NVIDIA PVA operators. It manages the end-to-end process of compiling source code, running emulator-based correctness checks, deploying to a connected Tegra device via SSH, and executing hardware-level system tests. The skill enforces strict input validation, requires documented references from a Doctor report, and produces detailed evidence-based reports in both Markdown and JSON formats.
What it does
- Validates input configurations and SDK references against a Doctor report.
- Performs emulator-based correctness testing for PVA operators.
- Compiles operators for L4T using specified NVVPU or ASIP/Chess backends.
- Deploys and executes system tests on target Tegra hardware via direct SSH.
- Collects and reports performance metrics when requested.
- Generates comprehensive build and test logs with verifiable evidence.
When to use it
- When you need to verify the correctness of a PVA operator build.
- When you require automated testing on physical Tegra hardware.
- When integrating operator verification into an OpGen workflow.
- When you need to generate standardized evidence reports for PVA operator builds.
Advantages
- Ensures consistent verification by requiring Doctor-approved references.
- Automates the transition from emulator testing to hardware deployment.
- Provides clear, evidence-based verdicts of PASSED, FAILED, or BLOCKED.
- Maintains strict separation between build, test, and deployment stages.
Usage examples
- “Run pva-build-test for operator my_op with correctness-only scope.”
- The agent validates the environment, builds the operator, runs the emulator and hardware tests, and generates a report confirming the operator's correctness.
- “Execute pva-build-test with correctness-and-performance for my_op.”
- The agent performs the full build and hardware test suite, collects performance profiling data, and includes the results in the final report.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/pva-build-test/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip pva-build-test.zip -d .agents/skills
Documentation by Venkat Balan
<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
Build and test a PVA operator
Build the current source. Test it on a directly connected Tegra. Do not change source code, expected results, or tolerances.
Build-Test owns verification stages, evidence, and verdicts.
Resolve paths
SKILL_ROOT is the absolute directory containing this skill's SKILL.md,
after resolving symlinks. Bundled files are relative to that directory. Resolve
supplied relative paths against the invocation directory before changing
directories. PROJECT_ROOT is the active source
workspace; RESULT_DIR is the caller's result directory. All build directories,
reports, logs, and manifests below are under RESULT_DIR, not the shell's CWD.
Get the inputs
Require these inputs for all scopes:
Caller identity:
OpGenfor an OpGen call; otherwise the direct user.A Doctor report that is ready for
build-test, or accepted limitations.Absolute project (
PROJECT_ROOT) and result (RESULT_DIR) paths.Operator name and PVA generation.
Test scope:
correctness-onlyorcorrectness-and-performance.Report label. Use
build-testwhen none is supplied.SDK version, safety variant, and Doctor's proved compiler backend.
EMU policy; when EMU execution is available or required, Doctor's proved EMU build mode and configure options, plus test commands.
L4T configure command and hardware system-test target and filter.
Correctness cases, independent references, and tolerances.
Complete install target or deployment manifest.
Tegra address, user, port, and persistent known-hosts file.
For correctness-and-performance, also require:
KPI or profiling target and case filter.
Profiling method, metric, warm-up count, and at least 1000 samples.
User-approved clock and clock-verification commands.
Expected clock values and target power mode.
Performance target and acceptance rule when the caller requests a comparison.
Do not require a KPI target, profiling artifact, clock input, sample count, or
performance filter for correctness-only.
Do not guess a command, target account, filter, expected result, clock setting, or acceptance rule.
Verify the inputs and references
Require Doctor's public-reference-corpus check to be PASS. Set
SDK_REFERENCES to the report's absolute sdk_reference_root. Require a readable
index.md and reference-lock.json, a lock SHA-256 matching the report's
sdk_reference_lock_sha256, and the reported SDK version matching this task.
If these fields are absent or no longer match, return BLOCKED and request a
fresh Doctor report. Do not fall back to an installed package or CWD path. Read the
pva-build-test route in $SDK_REFERENCES/index.md.
Before reading Markdown, check its SHA-256 against the lock
outputs entry; return BLOCKED on a mismatch. Resolve links relative to each
generated file. Use rg to
select relevant build, compiler, deployment, signing, EMU, and
profiling Markdown.
Read the direct-SSH procedure before target access. Fill the JSON result template using the result rules, then write the Markdown report from the same values.
Validate:
Absolute and readable project paths and a writable result path.
At least one correctness case with an independent expected result.
Unambiguous build, test, deployment, and target commands.
At least one matching hardware system test.
Performance inputs only when performance is in scope.
PVA generation, SDK runtime, and safety-variant consistency.
Return BLOCKED for a missing or ambiguous required input.
For each product fact, record the SDK documentation root, local Markdown path, packaged source path, source SHA-256, version, and section or PDF page.
Protect evidence
Before the build:
Create new build directories under the result directory.
Write
source-manifest-before.sha256with paths relative to the project root. Exclude new build and result directories.Record Git identity and dirty state when Git metadata exists.
Record each command, exit code, log, and principal artifact hash.
Do not reuse a build, log, target result, or profile from an earlier source state.
Run the stages
Run these stages in order:
| Stage | Required action |
|---|---|
| Input | Validate inputs, source identity, references, and scope. |
| EMU build | If EMU is available or required, create a fresh build using Doctor's proved EMU mode and configure options. Otherwise record SKIPPED_OPTIONAL. |
| EMU test | Run the approved EMU cases. Stop with FAILED on a demonstrated source or result defect. |
| L4T build | Create a fresh release build with PVA_BUILD_MODE=L4T, the requested generation, PVA_DISASSEMBLE=ON, and Doctor's proved NVVPU or ASIP/Chess backend. |
| Listing | Record and inspect the generated compiler listing. Confirm vectorization in the main data path. |
| Target probe | Use the direct-SSH procedure. Confirm Arm64, BSP, runtime version, safety variant, libraries, and required permissions. |
| Deploy | Stage and transfer an explicit archive. Check dynamic dependencies on the target. |
| Hardware test | List and run the filtered system tests for the complete correctness matrix. |
| Performance | Run only for correctness-and-performance, after hardware correctness passes. |
| Freshness | Hash the final source and compare it with the initial manifest. |
EMU rules
Use PVA_BUILD_MODE=EMU with Doctor's proved SDK, generation, compiler, and
other EMU configure options. Keep the L4T compiler selection separate.
Replace the probe's source and build paths with PROJECT_ROOT and a new
directory under RESULT_DIR;
use the project's supplied test targets. Record the selected mode and options
in emulator and the full command in commands.log. Return BLOCKED
if an available or required EMU backend lacks this evidence or its settings
conflict with the requested SDK or generation. Do not substitute another host
execution tool for EMU.
With policy optional, an unavailable EMU component is
SKIPPED_OPTIONAL. An EMU stage that starts and shows a source, build, or
result defect is FAILED.
With policy required, an unavailable EMU component is BLOCKED.
EMU execution is an early correctness aid. It is not hardware evidence.
Run the same approved correctness cases, inputs, references, and tolerances on EMU and hardware when EMU runs. Do not reduce the EMU matrix because it is slow. Record the case IDs and counts for both environments.
L4T and compiler rules
Build the hardware system-test executable for both scopes. Build the KPI or
profiling executable only for correctness-and-performance.
Accept the NVVPU or ASIP/Chess backend that Doctor proved. Do not require an
ASIP path or Synopsys license when NVVPU is selected. Return BLOCKED if the
proved backend is no longer usable. Return FAILED when current source causes
the build to fail.
Require the compiler listing after a successful build. Record its path, hash,
generation, entry point, main vector operations, address-generation evidence,
spills, warnings, and scheduling facts that affect correctness. Return
FAILED if the main data path is not vectorized.
Deployment rules
Use a project install target when it creates a complete deployment tree. Otherwise, use the supplied manifest.
Always include the hardware system-test executable, project libraries, device
data, and test assets. Include the KPI or profiling executable and its assets
only for correctness-and-performance.
Do not copy host-architecture libraries. Retain the remote directory unless the user asks for its removal.
Hardware correctness rules
Run --gtest_list_tests with the approved filter. Reject a zero-match filter.
Then run the same filtered system-test executable.
For each case, record the input shape, format, pitch, parameters, independent reference, tolerance, exit code, comparison, and maximum error when relevant.
Return FAILED if the process, command status, output, case coverage, or
tolerance check fails. Do not use a KPI-binary pass as correctness evidence.
Performance rules
Skip this stage for correctness-only.
For correctness-and-performance:
Run the approved clock command and verify clocks and power mode.
Run warm-ups separately.
Collect at least 1000 hardware samples with the approved public profiling method.
Verify clocks and power mode again.
Record the metric, unit, workload, warm-ups, samples, minimum, maximum, mean, median, target conditions, and raw data path.
Compare with a target only when the caller supplied a target and acceptance rule.
Do not use EMU time, host wall time, or total test duration as PVA execution time. Do not derive a target from the implementation under test.
A missed target is FAILED only when the acceptance rule makes it required.
Decide the verdict
PASSED: Every stage required by the selected scope passed for the current source. An optional EMU stage can beSKIPPED_OPTIONAL.FAILED: A stage ran and produced a negative source, build, correctness, vectorization, or required performance result.BLOCKED: A required stage could not run because an external input, dependency, permission, corpus, or target was unavailable.
Do not return PASSED from evidence for another source state. Do not change
BLOCKED to PASSED because EMU tests passed.
Write the outputs
Always write:
reports/<report-label>.mdreports/<report-label>.jsonsource-manifest-before.sha256source-manifest.sha256source-identity.txtcommands.log
Write stage logs and artifact hashes only for stages that run. For
correctness-only, do not require clock, profile, KPI, or raw performance
files. If work stops early, mark later stages NOT_RUN and name the exact
failed or blocked stage.
Do not remove raw evidence or replace it with a summary.
Return control
Return the verdict and absolute report paths to the caller. When called by
OpGen, continue the existing OpGen workflow before ending the overall run:
FAILED with remaining attempts goes to Debug; zero or exhausted attempts go
to OpGen's final FAILED report. PASSED and BLOCKED also require OpGen's
final report. Do not reinvoke OpGen or end with only a Build-Test response.
Files
- ATTRIBUTION.mdAdded by AutoGineer940 B
- BENCHMARK.md9.8 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- README.md7.6 KiB
- SKILL.md10.7 KiB
- agents/openai.yaml398 B
- assets/build-test-result-template.json3.0 KiB
- config/skillspector-baseline.yaml400 B
- evals/EVAL.md1.4 KiB
- evals/config.yml167 B
- evals/evals.json4.2 KiB
- evals/files/emu-only/emu.log131 B
- evals/files/unverified/doctor-report.md278 B
- references/build-test-result-schema.md1.5 KiB
- references/direct-ssh-tegra.md5.6 KiB
- skill-card.md4.7 KiB
- skill.oms.sig6.8 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Venkat Balan
- Publisher
- NVIDIA (Official)
- Distributed by
- NVIDIA
- Source
- NVIDIA/skills · skills/pva-build-test · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Venkat Balan or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download pva-build-test.zip