Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos.

Using workflow run logs

You can view, search, and download the logs for each job in a workflow run.

GitHub Actions se encuentra disponible con GitHub Free, GitHub Pro, GitHub Free para organizaciones, GitHub Team, GitHub Enterprise Cloud, y GitHub One. GitHub Actions no se encuentra disponible para repositorios privados que pertenezcan a cuentas que utilicen planes tradicionales por repositorio. Para obtener más información, consulta la sección "Productos de GitHub".

En este artículo

You can see whether a workflow run is in progress or complete from the workflow run page. You must be logged in to a GitHub account to view workflow run information, including for public repositories. For more information, see "Access permissions on GitHub."

If the run is complete, you can see whether the result was a success, failure, canceled, or neutral. If the run failed, you can view and search the build logs to diagnose the failure and re-run the workflow. You can also view billable job execution minutes, or download logs and build artifacts.

GitHub Actions use the Checks API to output statuses, results, and logs for a workflow. GitHub creates a new check suite for each workflow run. The check suite contains a check run for each job in the workflow, and each job includes steps. GitHub Actions are run as a step in a workflow. For more information about the Checks API, see "Checks."

Nota: Garantiza que solo confirmes los archivos de flujo de trabajo válidos en tu repositorio. Si .github/workflows contiene un archivo de flujo de trabajo inválido, GitHub Actions generará una ejecución de flujo de trabajo fallida por cada confirmación nueva.

Viewing logs to diagnose failures

If your workflow run fails, you can see which step caused the failure and review the failed step's build logs to troubleshoot. You can see the time it took for each step to run. You can also copy a permalink to a specific line in the log file to share with your team. Las personas con acceso de lectura en el repositorio pueden llevar a cabo estos pasos.

In addition to the steps configured in the workflow file, GitHub adds two additional steps to each job to set up and complete the job's execution. These steps are logged in the workflow run with the names "Set up job" and "Complete job".

For jobs run on GitHub-hosted runners, "Set up job" records details of the runner's virtual environment, and includes a link to the list of preinstalled tools that were present on the runner machine.

  1. En GitHub, visita la página principal del repositorio.

  2. Debajo del nombre de tu repositorio, da clic en Acciones.

    Pestaña de acciones en la navegación del repositorio principal

  3. In the left sidebar, click the workflow you want to see.

    Workflow list in left sidebar

  4. From the list of workflow runs, click the name of the run you want to see.

    Name of workflow run

  5. In the left sidebar, click the job you want to see.

    Lint code base job

  6. Any failed steps are automatically expanded to display the results.

    Super linter workflow results

  7. Optionally, to get a link to a specific line in the logs, click on the step's line number. You can then copy the link from the address bar of your web browser.

    Button to copy link

Searching logs

You can search the build logs for a particular step. When you search logs, only expanded steps are included in the results. Las personas con acceso de lectura en el repositorio pueden llevar a cabo estos pasos.

  1. En GitHub, visita la página principal del repositorio.

  2. Debajo del nombre de tu repositorio, da clic en Acciones.

    Pestaña de acciones en la navegación del repositorio principal

  3. In the left sidebar, click the workflow you want to see.

    Workflow list in left sidebar

  4. From the list of workflow runs, click the name of the run you want to see.

    Name of workflow run

  5. In the left sidebar, click the job you want to see.

    Lint code base job

  6. In the upper-right corner of the log output, in the Search logs search box, type a search query.

    Search box to search logs

Downloading logs

You can download the log files from your workflow run. You can also download a workflow's artifacts. For more information, see "Persisting workflow data using artifacts." Las personas con acceso de lectura en el repositorio pueden llevar a cabo estos pasos.

  1. En GitHub, visita la página principal del repositorio.

  2. Debajo del nombre de tu repositorio, da clic en Acciones.

    Pestaña de acciones en la navegación del repositorio principal

  3. In the left sidebar, click the workflow you want to see.

    Workflow list in left sidebar

  4. From the list of workflow runs, click the name of the run you want to see.

    Name of workflow run

  5. In the left sidebar, click the job you want to see.

    Lint code base job

  6. In the upper right corner, click and select Download log archive.

    Download logs drop-down menu

Deleting logs

You can delete the log files from your workflow run. Las personas con acceso de escritura en el repositorio pueden llevar a cabo estos pasos.

  1. En GitHub, visita la página principal del repositorio.

  2. Debajo del nombre de tu repositorio, da clic en Acciones.

    Pestaña de acciones en la navegación del repositorio principal

  3. In the left sidebar, click the workflow you want to see.

    Workflow list in left sidebar

  4. From the list of workflow runs, click the name of the run you want to see.

    Name of workflow run

  5. In the upper right corner, click .

    Kebab-horizontal icon

  6. To delete the log files, click the Delete all logs button and review the confirmation prompt.

    Delete all logs
    After deleting logs, the Delete all logs button is removed to indicate that no log files remain in the workflow run.

¿Te ayudó este documento?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

O, learn how to contribute.