Skip to content

ci-failure: aiostreams/dev upstream-rebase #767

Description

@chloeobot

CI failure: aiostreams/dev

Streak: 5 consecutive scheduled runs
Category: upstream-rebase
Run: https://github.com/elfhosted/containers/actions/runs/29359394710

Note: automation attempted to apply label ci-failure, but GitHub reported the label does not exist and the token could not create it.

Failure: 01-replay.patch no longer applies against upstream packages/core/src/builtins/newznab/addon.ts.

Log excerpt

#28 [cloner 4/7] COPY apps/aiostreams/dev/patches/ /patches/
#28 DONE 0.0s
#29 [cloner 5/7] RUN set -e; cd /source; for p in /patches/*.patch; do echo "Applying $p..."; git apply "$p"; done
#29 0.060 Applying /patches/01-replay.patch...
#29 0.066 error: patch failed: packages/core/src/builtins/newznab/addon.ts:9
#29 0.066 error: packages/core/src/builtins/newznab/addon.ts: patch does not apply
#29 ERROR: process "/bin/sh -c set -e; cd /source; for p in /patches/*.patch; do echo \"Applying $p...\"; git apply \"$p\"; done" did not complete successfully: exit code: 1

Suggested fix

  • Rebase containers-private/apps/aiostreams/dev/patches/01-replay.patch against upstream commit 55b1412448221a40f295b9999dc3356e75f3b8e2.
  • Check upstream git log -p -- packages/core/src/builtins/newznab/addon.ts for the changed hunk around line 9 before refreshing the patch.

Priority: high (blocking releases)

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