Skip to content

TP · Capturas de cada ejecución en el informe (regla del docente) - #51

Merged
R0SEWT merged 1 commit into
developfrom
feature/tp-capturas
Oct 4, 2026
Merged

R0SEWT merged 1 commit into
developfrom
feature/tp-capturas

Conversation

@R0SEWT

@R0SEWT R0SEWT commented Oct 4, 2026 •

Copy link
Copy Markdown
Owner

El docente pide una captura de pantalla de cada ejecución; una ejecución que solo se nombra o aparece como listado cuenta como no demostrada. De ahí vinieron las observaciones de la PC2.

Qué cambia

  • tp/scripts/capturar_ejecuciones.sh: corre cada ejecución, guarda su salida real en img/ejec-*.txt (primera línea: el comando) y la renderiza con capturas_terminal.py. Se puede rehacer por grupos: datos, go, spin, benchmark, ci.
  • Nuevas figuras: pipeline y pytest (Sec. 5), go vet + go test -race completo (Sec. 8), benchmark reducido de demostración (Sec. 10), checks de CI de la PR TP · Cierre del Entregable 3: visor rediseñado, capturas regenerables y PRs del grupo en el informe #50 (Sec. 14), make check de Spin (Sec. 17).
  • Las salidas de pan de las Secciones 7 y 17 pasan de listados de texto a capturas con su comando.

Verificación

  • pytest: 66 pasan. nyc-tlc all: gold con el mismo sha256 (a3ad5205…).
  • go vet y go test -race -count=1 ./... sin -short: ok (≈160 s).
  • make check: 7/7 casos.
  • El informe compila sin errores (80 páginas).

Notas

Summary by Sourcery

Add reproducible execution captures throughout the report to provide direct evidence for every documented verification run.

New Features:

  • Add a reproducible script for running and rendering evidence from data, Go, Spin, benchmark, and CI executions.
  • Include captured execution outputs as figures throughout the report to demonstrate each required run.

Enhancements:

  • Replace text listings of Spin executions and deadlock traces with terminal-capture figures.
  • Clarify that the benchmark capture is a reduced demonstration while official tables use the full benchmark run.

Documentation:

  • Document how to regenerate all execution captures or selected capture groups.

El docente exige una captura de pantalla de cada ejecución: una que solo se
nombra en el texto o aparece como listado cuenta como no demostrada, y de ahí
salieron las observaciones de la PC2. tp/scripts/capturar_ejecuciones.sh corre
el pipeline, pytest, go vet + go test -race, la regresión de Spin, un benchmark
reducido y los checks de CI de la PR #50, guarda la salida real en
img/ejec-*.txt y la renderiza con capturas_terminal.py.

Las salidas de pan de las Secciones 7 y 17 pasan de listados a figuras con su
comando, y las Secciones 5, 8, 10, 14 y 17 suman la captura de la ejecución
que antes solo nombraban.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @R0SEWT, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 3 days by commenting @sourcery-ai review. Upgrade to get a review now.

@sourcery-ai

sourcery-ai Bot commented Oct 4, 2026

Copy link
Copy Markdown

Reviewer's Guide

El PR agrega un flujo reproducible para ejecutar y capturar cada verificación exigida, y actualiza el informe para presentar esas capturas como evidencia —incluidas las ejecuciones de datos, Go, Spin, benchmark y CI— en lugar de simples listados o menciones.

Flow diagram for reproducible execution captures

flowchart TD
    A[capturar_ejecuciones.sh] --> B{Selected groups}
    B --> C[datos]
    B --> D[go]
    B --> E[spin]
    B --> F[benchmark]
    B --> G[ci]
    C --> H[Run data pipeline and pytest]
    D --> I[Run go vet and go test -race]
    E --> J[Run Spin regression and pan outputs]
    F --> K[Run reduced benchmark]
    G --> L[Run gh pr checks 50]
    H --> M[Write ejec-*.txt]
    I --> M
    J --> M
    K --> M
    L --> M
    M --> N[capturas_terminal.py]
    N --> O[Render ejec-*.png]
Loading

File-Level Changes

Change Details Files
Automatiza la generación de capturas reproducibles para cada ejecución relevante del informe.
  • Añade un script con grupos seleccionables para ejecutar datos, Go, Spin, benchmark y checks de CI.
  • Guarda el comando y la salida real en archivos de texto y los convierte en imágenes terminales.
  • Documenta requisitos, uso y regeneración total o por grupo.
tp/scripts/capturar_ejecuciones.sh
tp/informe/tp/README.md
tp/informe/tp/img/ejec-*.txt
Integra evidencias gráficas de ejecuciones en las secciones técnicas del informe. tp/informe/tp/secciones/05-limpieza.tex
tp/informe/tp/secciones/08-implementacion-go.tex
tp/informe/tp/secciones/10-speedup.tex
tp/informe/tp/secciones/14-github.tex
tp/informe/tp/secciones/17-verificacion-formal.tex
tp/informe/tp/secciones/07-algoritmo-promela.tex
tp/informe/tp/img/ejec-*.txt

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@R0SEWT
R0SEWT merged commit 712839b into develop Oct 4, 2026
4 checks passed
@R0SEWT
R0SEWT deleted the feature/tp-capturas branch October 4, 2026 00:19
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