Skip to content

Jb/omnibus ci#739

Open
jon5000 wants to merge 4 commits intomainfrom
jb/omnibus-ci
Open

Jb/omnibus ci#739
jon5000 wants to merge 4 commits intomainfrom
jb/omnibus-ci

Conversation

@jon5000
Copy link
Collaborator

@jon5000 jon5000 commented Feb 24, 2026

Description

This workflow starts the omnibus process, bootstrapping from epoch 507 and using Mithril to sync, then monitors the process using the REST interface until the target epoch is reached. The current Cardano epoch is the default target epoch, but this can be changed by submitting a different epoch as the input to Begin tests when the omnibus process reaches this epoch when running the workflow manually.

Once the target epoch is reached, integration tests are carried out on SPDD and DRDD, then the k6 framework is used to perform a smoke test.

The workflow is scheduled to start at 03:15 which should generally be after the completion of the working day for the team. It can also be manually triggered by team members on any branch to facilitate testing before merging.

Related Issue(s)

Relates to #637

How was this tested?

By selecting Run omnibus bootstrap test in github actions, then Run workflow' and choosing this branch, then using 520 as the input to Begin tests when the omnibus process reaches this epoch.

Checklist

  • My code builds and passes local tests
  • I added/updated tests for my changes, where applicable
  • I updated documentation (if applicable)
  • branch has ≤ 5 commits (honor system)
  • commit messages tell a coherent story
  • branch is up to date with main (rebased on main; fast-forward possible)
  • CI/CD passes on the merged-with-main result

Impact / Side effects

Various aspects of the workflow and the tests are currently dependent on mainnet being the target network. Further work needs to be done to make this generic and applicable to other networks.

Reviewer notes / Areas to focus

@buddhisthead
Copy link
Collaborator

Hi Jon, can you update the PR description with a statement about what this script does and why we need it? Thanks! It will be helpful in the future.

@buddhisthead
Copy link
Collaborator

Is this connected to PR pushes yet? Or nightly runs? I was imagining that I'd see the test results run on this very branch as a proof that it works.

jon5000 added 4 commits March 18, 2026 22:19
Various thresholds will be exceeded with the current omnibus config,
resulting in an error exit and follow-on tests not being run.
Thresholds should be re-enabled once we have the relevant config enabled.
@buddhisthead
Copy link
Collaborator

buddhisthead commented Mar 20, 2026

Hi Jon, I love that you added Makefile entries for the tests. I wonder if you plan to update the README or some other documentation to describe how to manually start the tests for main or other branches?

Along with that, the PR description should tell me how to test this PR, which I do not see (or know how to do without thinking harder). Can you please update the "How to Test" section?

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.

2 participants