Skip to content
This repository was archived by the owner on Nov 21, 2026. It is now read-only.
This repository was archived by the owner on Nov 21, 2026. It is now read-only.

Stage order: moved-version engines in tier 2, ArcadeDB lifecycle/restart/image-defaults behind the core tier-2 stages #225

Closed

Description

@tae898

The user adopted both recommendations of the #223 exchange (2026-10-06, DECISIONS #165). Tier 2 now includes the engines whose version moved since October's rows (ArangoDB 3.12.12, FalkorDB 6.0.1, LadybugDB 0.21.2), which run at the versions already in runner.py; tier 3 holds only arms with no October rows. ArcadeDB's lifecycle, restart and image-defaults arms run after the core tier-2 stages, then the lifecycle and restart comparators, so the core comparisons land first. The order is tier 1 core, tier 2 core, tier 1 extras, tier 2 extras, tier 3; 34 stages instead of 37.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions