Skip to content

Retry the AnyBlox reproducibility artifact #40

Closed as not planned
Closed as not planned

Description

@Anionix

Retry pinned AnyBlox evidence from #16 when the artifact pins a reproducible nightly Rust toolchain or builds on stable. Require official bundler and anyblox2csv round-trip evidence.

Activity

  1. Anionix commented on Jul 16, 2026

    @Anionix
    OwnerAuthor

    Revalidation status (2026-07-17 JST)

    No new retry was promoted to a benchmark. The AnyBlox reproducibility artifact is still at 3cf5008b4af5165761021b9f6f24d326d83d2a56 on its default branch, matching the recorded artifact pin. The existing evidence remains that the vendored Vortex path requires unversioned nightly Rust features and does not build with stable Rust.

    Because the retry contract requires a reproducible nightly toolchain pin or a stable-Rust build plus official bundler and anyblox2csv round-trip, this issue remains needs-info and stays UNAVAILABLE for ranking.

  2. Anionix commented on Jul 16, 2026

    @Anionix
    OwnerAuthor

    Retry result (2026-07-17 JST)

    PR #166 is merged. The pinned artifact still contains official bundler and anyblox2csv targets, but the Rust toolchain is an undated nightly channel and the checksum-complete input dataset/.anyblox bundle is not available. This host has stable Rust 1.93.1 without rustup; compilation fails with E0554/E0599, so no round trip or performance result ran.

    The evidence remains FAILED / PARTIAL and is excluded from ranking. This issue stays open with needs-info; the next retry requires an exact nightly toolchain or stable build plus a checksum-complete input bundle and official bundler-to-reader round trip.

  3. Anionix commented on Jul 16, 2026

    @Anionix
    OwnerAuthor

    Public-source audit (2026-07-17 JST)

    AnyBlox remains UNAVAILABLE for ranking and no benchmark retry is promoted.

    The artifact remains pinned at 3cf5008b4af5165761021b9f6f24d326d83d2a56, with core 02447f8b5dff3cee53ecc82f2992355b0600fa05. The source contains official bundler and anyblox2csv targets, but the toolchain is only an undated nightly channel and the dataset download path does not publish checksum-complete input/.anyblox artifacts.

    A lab-side nightly pin does not repair upstream provenance by itself. The existing stable build failure and absent frozen input bundle therefore remain FAILED / PARTIAL evidence, excluded from rankings.

    Next retry gate: an exact nightly toolchain or stable build, plus checksum-complete inputs and a successful official bundler-to-reader round trip.

  4. Anionix commented on Jul 16, 2026

    @Anionix
    OwnerAuthor

    Current upstream closure check (2026-07-17 JST)

    The official AnyBlox HEAD still resolves to the recorded artifact commit . The artifact still exposes only an undated nightly Rust channel and no checksum-complete input bundle is available in the lab. No new reader/writer retry is reproducible yet, so this remains and excluded from ranking.

  5. Anionix commented on Jul 16, 2026

    @Anionix
    OwnerAuthor

    Correction to the previous comment

    The previous comment was shell-escaped incorrectly. The authoritative result is:

    The official AnyBlox HEAD still resolves to the recorded artifact commit 3cf5008b4af5165761021b9f6f24d326d83d2a56. The artifact still exposes only an undated nightly Rust channel, and no checksum-complete input .anyblox bundle is available in the lab. No new reader/writer retry is reproducible yet, so this remains needs-info and excluded from ranking.

  6. Anionix commented on Jul 16, 2026

    @Anionix
    OwnerAuthor

    Current v0.1 closure

    PR #166 and the follow-up evidence are merged, and the machine-readable record is research/formats/anyblox.json.

    • official bundler and anyblox2csv targets are present
    • the artifact requests an undated nightly Rust channel without a reproducible pin
    • stable Rust fails with E0554/E0599
    • no checksum-complete input dataset and .anyblox bundle are available
    • no round trip or performance result can be measured or ranked

    Closing this retry issue as not planned for the current v0.1 scope. Reopen when an exact nightly or stable build and checksum-complete inputs support the official bundler-to-reader round trip. No ranking result is implied.

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

    needs-infoNeeds more information

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions