table

Failed after

LCLachlan Collins

ci: use voidzero-dev/setup-vp directly

66450b47872Open on GitHub

Self-Healing CI

Classification: Environment state

We looked at the failing @tanstack/angular-table:test:types task, and it doesn't look related to our change. This PR only switches our CI workflows to use voidzero-dev/setup-vp directly and touches no package source or tests, so we're not proposing a fix here.

An empty commit was applied to the branch to trigger a new CI pipeline execution to resolve the environment issue.

This failure was not classified as a code_change, for these reasons:

  1. The PR only changes CI setup.
  • It replaces the custom setup action with voidzero-dev/setup-vp in the workflows.
  • touched_projects is empty, so no package source or test code was modified.
  1. The error does not point at anything the PR changed.
  • The failing task is @tanstack/angular-table:test:types.
  • One test fails: tests/lazy-init.test.ts > "should init lazily and only once".
  • The assertion is expected vi.fn() to be called 1 times, but got 2 times.
  • The type check reported no errors, and the other 59 tests passed.
  • Nothing in the error references workflow files or setup steps.
  1. The task is not flaky.
  • The flakiness rate is 0%, so it cannot be classified as flaky_task.
  1. The base-branch comparison was inconclusive.
  • The similar-failures tool returned no results for main, so the failure could not be matched to it.
  • This was not used as evidence either way.
  1. The default rule applies.
  • The failing project is not in touched_projects, so the fallback is environment_state.
  • The failure is deterministic and exists independently of this PR.

No changes are proposed. If the lazy-init test needs a fix, it belongs in a separate change.