Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

gfxgraph-testing

Estrellas0

Forks1

Actualizado17 de mayo de 2026 a las 06:17

Test gfxGRAPH on real hardware and confirm it is functioning after install or configuration changes.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

carlosfundora

carlosfundora/gfxGRAPH

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

SKILL.md

readonly

name	gfxgraph-testing
description	Test gfxGRAPH on real hardware and confirm it is functioning after install or configuration changes.

gfxGRAPH Testing

Goal Confirm gfxGRAPH is functioning on the target machine after install or reconfiguration.

When to use this skill

After installing gfxGRAPH.
After changing configuration or replay modes.
When you need to confirm the package actually works on a real ROCm GPU.
When you need a pass/fail answer for the current install state.

Do not use this skill for

Preparing the environment for install.
Applying configuration changes.
Debugging unrelated ROCm failures before the install is proven.

How to use it

Run the relevant Python integration tests from the repo.
Run a direct smoke check with gfxgraph.health_check().
Confirm the runtime reports the expected GPU and replay behavior.
If a failure appears, capture the exact error before changing anything else.

Preferred checks

python3 -m pytest tests/test_torch_integration.py -v
python3 -c "import gfxgraph; gfxgraph.enable(); print(gfxgraph.health_check())"
gfxgraph.stats() after a real capture/replay path

Test rules

Use real hardware when available.
Do not rely on mocks for GPU availability in the success path.
Confirm both importability and runtime behavior.
Prefer a minimal smoke test first, then expand to the repo's integration test path.

Pass criteria

import gfxgraph succeeds.
gfxgraph.health_check() reports ok: True.
The runtime sees the intended ROCm GPU.

Más de este repositorio

mismo repositorio

gfxgraph-development

carlosfundora/gfxGRAPH

Develop and extend gfxGRAPH internals — add gap bridges, fix HIP/ROCm issues, debug graph capture failures, and understand the architecture. Covers BridgedCUDAGraph, ShapeBucketPool, ConditionalGraph, native bridge, and the monkey-patch system. USE FOR: extend gfxGRAPH, add new gap bridge, fix gfxGRAPH bug, understand gfxGRAPH architecture, modify BridgedCUDAGraph, add gfxGRAPH feature, debug graph capture internals, improve gfxGRAPH performance, gfxGRAPH C++ native bridge, write gfxGRAPH tests. DO NOT USE FOR: just using gfxGRAPH in a project (use gfxgraph-integration), general ROCm issues.

2026-07-240

gfxgraph-benchmarking

carlosfundora/gfxGRAPH

Benchmark gfxGRAPH internals, run the public benchmark suite, and compare performance between Python and Rust.

2026-07-240

rocm-atom-inference

carlosfundora/gfxGRAPH

Guide and resources for deployment and development using the ROCm/AMD ATOM (AiTer Optimized Model) inference backend.

2026-07-240

benchmark-validate

carlosfundora/gfxGRAPH

Validates and benchmarks ROCm-DS component ports against their CPU baselines (e.g., pandas vs hipDF). Use this to generate parity tests, verify correctness, and measure the performance speedups of GPU-accelerated code.

2026-07-240

compatibility-triage

carlosfundora/gfxGRAPH

Verifies whether a requested ROCm-DS workflow is officially supported, source-build feasible, or experimental on the target system.

2026-07-240

hipdf-pandas-port

carlosfundora/gfxGRAPH

Migrates pandas-like workflows to hipDF and cudf.pandas style acceleration, auditing for unsupported features.

2026-07-240

name	gfxgraph-testing
description	Test gfxGRAPH on real hardware and confirm it is functioning after install or configuration changes.

gfxGRAPH Testing

Goal Confirm gfxGRAPH is functioning on the target machine after install or reconfiguration.

When to use this skill

After installing gfxGRAPH.
After changing configuration or replay modes.
When you need to confirm the package actually works on a real ROCm GPU.
When you need a pass/fail answer for the current install state.

Do not use this skill for

Preparing the environment for install.
Applying configuration changes.
Debugging unrelated ROCm failures before the install is proven.

How to use it

Run the relevant Python integration tests from the repo.
Run a direct smoke check with gfxgraph.health_check().
Confirm the runtime reports the expected GPU and replay behavior.
If a failure appears, capture the exact error before changing anything else.

Preferred checks

python3 -m pytest tests/test_torch_integration.py -v
python3 -c "import gfxgraph; gfxgraph.enable(); print(gfxgraph.health_check())"
gfxgraph.stats() after a real capture/replay path

Test rules

Use real hardware when available.
Do not rely on mocks for GPU availability in the success path.
Confirm both importability and runtime behavior.
Prefer a minimal smoke test first, then expand to the repo's integration test path.

Pass criteria

import gfxgraph succeeds.
gfxgraph.health_check() reports ok: True.
The runtime sees the intended ROCm GPU.