Skip to content

FLAME end-to-end: partitioner fix, execution metadata, setup callback #154

FLAME end-to-end: partitioner fix, execution metadata, setup callback

FLAME end-to-end: partitioner fix, execution metadata, setup callback #154

Triggered via pull request March 25, 2026 03:37
Status Failure
Total duration 2m 6s
Artifacts

ci.yml

on: pull_request
Format check
14s
Format check
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

24 errors and 5 warnings
Test (OTP 27 / Elixir 1.18)
Process completed with exit code 2.
Test (OTP 27 / Elixir 1.18): test/dux/flame_test.exs#L89
test status returns cluster info (Dux.FlameTest)
Test (OTP 27 / Elixir 1.18): test/dux/flame_test.exs#L52
test distribute with FLAME workers full pipeline: spin up → distribute → compute (Dux.FlameTest)
Test (OTP 27 / Elixir 1.18): test/dux/flame_test.exs#L65
test distribute with FLAME workers group_by + summarise across FLAME workers (Dux.FlameTest)
Test (OTP 27 / Elixir 1.18): test/dux/flame_test.exs#L39
test spin_up + basic operations workers execute pipelines (Dux.FlameTest)
Test (OTP 27 / Elixir 1.18): test/dux/flame_test.exs#L28
test spin_up + basic operations spins up workers that are alive and in :pg (Dux.FlameTest)
Test (OTP 28 / Elixir 1.19)
Process completed with exit code 2.
Test (OTP 28 / Elixir 1.19): test/dux/flame_test.exs#L89
test status returns cluster info (Dux.FlameTest)
Test (OTP 28 / Elixir 1.19): test/dux/flame_test.exs#L52
test distribute with FLAME workers full pipeline: spin up → distribute → compute (Dux.FlameTest)
Test (OTP 28 / Elixir 1.19): test/dux/flame_test.exs#L65
test distribute with FLAME workers group_by + summarise across FLAME workers (Dux.FlameTest)
Test (OTP 28 / Elixir 1.19): test/dux/flame_test.exs#L28
test spin_up + basic operations spins up workers that are alive and in :pg (Dux.FlameTest)
Test (OTP 28 / Elixir 1.19): test/dux/flame_test.exs#L39
test spin_up + basic operations workers execute pipelines (Dux.FlameTest)
Test (OTP 28 / Elixir 1.18)
Process completed with exit code 2.
Test (OTP 28 / Elixir 1.18): test/dux/flame_test.exs#L89
test status returns cluster info (Dux.FlameTest)
Test (OTP 28 / Elixir 1.18): test/dux/flame_test.exs#L28
test spin_up + basic operations spins up workers that are alive and in :pg (Dux.FlameTest)
Test (OTP 28 / Elixir 1.18): test/dux/flame_test.exs#L39
test spin_up + basic operations workers execute pipelines (Dux.FlameTest)
Test (OTP 28 / Elixir 1.18): test/dux/flame_test.exs#L52
test distribute with FLAME workers full pipeline: spin up → distribute → compute (Dux.FlameTest)
Test (OTP 28 / Elixir 1.18): test/dux/flame_test.exs#L65
test distribute with FLAME workers group_by + summarise across FLAME workers (Dux.FlameTest)
Test (OTP 27 / Elixir 1.19)
Process completed with exit code 2.
Test (OTP 27 / Elixir 1.19): test/dux/flame_test.exs#L65
test distribute with FLAME workers group_by + summarise across FLAME workers (Dux.FlameTest)
Test (OTP 27 / Elixir 1.19): test/dux/flame_test.exs#L28
test spin_up + basic operations spins up workers that are alive and in :pg (Dux.FlameTest)
Test (OTP 27 / Elixir 1.19): test/dux/flame_test.exs#L52
test distribute with FLAME workers full pipeline: spin up → distribute → compute (Dux.FlameTest)
Test (OTP 27 / Elixir 1.19): test/dux/flame_test.exs#L39
test spin_up + basic operations workers execute pipelines (Dux.FlameTest)
Test (OTP 27 / Elixir 1.19): test/dux/flame_test.exs#L89
test status returns cluster info (Dux.FlameTest)
Format check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (OTP 27 / Elixir 1.18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (OTP 28 / Elixir 1.19)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (OTP 28 / Elixir 1.18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (OTP 27 / Elixir 1.19)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/