Skip to content

Seeded upgrade, Windows arm64: Share dialog gave no pairing offer in the remote-install lane, once #396

Closed as not planned

Description

@mubeda

What happened

On the push of the v0.17.0 release preparation to main (commit 3b74079), the job Seeded upgrade - Windows arm64 NSIS of the Seeded Packaged Desktop Upgrade workflow failed once (run 44556214352, first attempt).

  • The previous-stable and protected-baseline lanes passed in full: version, storage identity, project and pre-update backup.
  • The remote-install lane failed before any install: the packaged app's Share dialog was found and clicked, but no pairing offer appeared within the lane's 60 s wait. The harness reported "Remote verification pairing offer could not be generated (share UI found=true, clicked=true)", with widened: false in its trace.
  • No crash dump was produced. The remote lane's WebDriver output is withheld by design when the credential receipt is not published, so the artifact holds no page state for that minute.

What was checked

  • One rerun of the same job on the same commit passed.
  • The same job passed about three hours earlier on a commit with the same product code (the release preparation changes versions, the changelog and a Claude hook version constant only).
  • The same lane passed on Windows arm64 in the manual run that seeds from v0.8.0 (run 44556269066), started at the same time.

Why this is closed

One failure in three samples of that lane on that day, with no evidence of the cause and no reproduction. An agent cannot investigate it further from the retained evidence: the lane keeps no WebDriver log when it fails at this step. If it recurs, the useful next step is to let the harness keep a redacted page snapshot of the Share dialog when the pairing offer does not appear.

Activity

  1. mubeda commented on Nov 19, 2026

    @mubeda
    OwnerAuthor

    Closed as not planned: it failed once, passed on rerun and in two other samples of the same lane that day, and the retained evidence does not show a cause. Reopen with the run link if it recurs.

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

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions