oxidecomputer / oxidecomputer/omicron

check-opte-ver CI flake

Open
#4,085 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

development Test Flake
Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

This run seems to have been a spurious failure:
https://github.com/oxidecomputer/omicron/actions/runs/6167960563/job/16739738214?pr=4084

The output:

Run ./tools/ci_check_opte_ver.sh
  ./tools/ci_check_opte_ver.sh
  shell: /usr/bin/bash -e {0}
OPTE version mismatch:
Cargo.toml: 98d33125413f01722947e322f82caf9d22209434 (0.23.)
tools/opte_version: 0.23.173
Error: Process completed with exit code 1.

In context:

Screenshot 2023-09-12 at 9 40 30 PM

I am not sure what happened here. I see that the patch number looks wrong (0.23. vs. 0.23.173). The bash script appears to make a bunch of HTTP requests to the GitHub API to count this. I wonder if one of these failed? The script does not emit much output, either on success or failure. But rerunning the job (with no change to the repo) succeeded, so I suspect a transient GitHub issue.

This might be a candidate to rewrite as an xtask where it's easier to retry and report errors better?

Contributor guide

Open the contributing guide

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

The failure is in tools/ci_check_opte_ver.sh, which compares Cargo.toml with tools/opte_version; start by examining that script and the linked GitHub Actions job output. Inspect its GitHub API requests and error handling, then determine how the incomplete version value arose. Done means the cause is addressed and future transient failures provide useful diagnostics.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash, github-actions, rust
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.