Qiskit / Qiskit/documentation

Extended checks failed

Open
#5,286 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

infra 🏗️
Dominant language
Jupyter Notebook
Stars
106
Forks
223
Avg merge
1d 8h
Merged PRs (30d)
72

Description

Today's scheduled extended checks failed.

Please check the logs.

[!NOTE]
This issue was created by a GitHub action.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open the linked GitHub Actions run and inspect the logs for the failed scheduled extended checks. Identify which check failed and use its reported error as the starting point. Done means the extended checks complete successfully in a subsequent scheduled or rerun workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.