Skip to content

chore: CI probe for the actor-runtime branch (do not merge) - #1493

Closed
Pijukatel wants to merge 1 commit into
actor-runtimefrom
ci/actor-runtime-e2e-probe
Closed

Pijukatel wants to merge 1 commit into
actor-runtimefrom
ci/actor-runtime-e2e-probe

Conversation

@Pijukatel

Copy link
Copy Markdown
Contributor

Draft only. Opened to run the check and E2E workflows against the current actor-runtime head (5f20318, master merged in). Contains a single empty commit; close once the results are read.

🤖 Generated with Claude Code

https://claude.ai/code/session_015JzfLYa5CHCXxfzC1No3gV


Generated by Claude Code

Empty commit so a draft pull request can run the check and E2E workflows
against the current actor-runtime head.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015JzfLYa5CHCXxfzC1No3gV

Copy link
Copy Markdown
Contributor Author

E2E Tests (ubuntu-latest) is red here, but not because of this branch.

  • The only failure is test/e2e/commands/actors/info.test.ts > shows input schema with --input flag: apify actors info apify/rag-web-browser --input prints Error: No input schema found for this Actor. instead of JSON, so JSON.parse on stdout throws.
  • The same test fails identically on master's scheduled E2E runs on the current master head 59dc6b0 (run 38212587354) and on every recent PR run. src/commands/actors/info.ts and the test are byte-identical between master and actor-runtime.
  • Everything else in the E2E job passed (102 tests). No fix exists yet; it looks like the public apify/rag-web-browser latest build no longer exposes inputSchema through the builds API, which is a test-data or platform question rather than a CLI one. Not re-running, since the failure is already reproduced across independent runs.

Generated by Claude Code

Copy link
Copy Markdown
Contributor Author

Local Tests (windows-2025, 24) is red for a reason that is this branch's, unlike the E2E one above:

  • test/local/lib/runtime-source-context.test.ts: expected roots built with join('/repo') give \repo on Windows, while resolveDockerContext resolves to D:\repo.
  • test/local/commands/push-monorepo.test.ts:311: expects tarball mode 0o755 after chmod, but Windows has no execute bit, so the archive records 0o666 (438 vs 493).

Both are test assumptions, not CLI bugs; the ubuntu jobs pass. Fix in #1494, not ported here since this PR is a probe and will be closed.


Generated by Claude Code

@Pijukatel Pijukatel closed this Oct 12, 2026
@Pijukatel
Pijukatel deleted the ci/actor-runtime-e2e-probe branch October 12, 2026 12:06
Pijukatel added a commit that referenced this pull request Oct 12, 2026
## What

The CI probe [#1493](#1493)
showed `Local Tests (windows-2025)` red on `actor-runtime` because two
branch-only tests assume POSIX paths and modes. The CLI code is fine on
Windows; only the assertions were wrong.

- `test/local/lib/runtime-source-context.test.ts`: expected roots were
built with `join('/repo')`, which is `\repo` on Windows, while
`resolveDockerContext` uses `resolve()` and gets `D:\repo`. The test now
resolves the same way.
- `test/local/commands/push-monorepo.test.ts`: the tarball mode
assertion expected `0o755` after `chmod`, but Windows has no execute
bit, so the archive records `0o666`. That one assertion is skipped on
Windows, as the existing mode tests in `auth-file` and `credentials`
already do; the rest of the test still runs there.

Test-only change; no CLI behavior changes.

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants