Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests(pd): automated migration testing #4337

Closed
wants to merge 2 commits into from
Closed

Commits on May 30, 2024

  1. tests(pd): automated migration testing

    Adds intra-CI standalone testing of migration behavior.
    This can be run locally on developer workstations,
    and also in CI. The job is currently taking >20m, and requires
    a lot of disk space, but it's worth it for the assurance.
    
    Building on the smoke-test rewrite to use process-compose,
    let's script the migration process, so that we can test
    current HEAD of the monorepo against a prior tagged version,
    and validate that necessary migrations are in place.
    
    One possible approach is to fetch prebuilt binaries from uploaded
    artifacts on Github. That's fine for `pd`, but doesn't work for
    running the smoke tests, due to client/server incompatibility.
    Therefore we'll clone the entire repo in a git-ignored subdir,
    and build the old binaries there. Heavy, but reliable.
    
    Adds a new rust crate, strictly for running the migration-test
    suite of integration tests, which is very similar in nature to the
    already-existing network-integration tests AKA smoke tests.
    Copy/pastes a lot of code from the smokes, which we can always
    factor out into reusable utils, but not bothering with that right now.
    
    Refs #4323.
    conorsch committed May 30, 2024
    Configuration menu
    Copy the full SHA
    af07e4f View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    2a6ee60 View commit details
    Browse the repository at this point in the history