Skip to content

Merge pull request #88 from golemcloud/stack-overflow-debug #308

Merge pull request #88 from golemcloud/stack-overflow-debug

Merge pull request #88 from golemcloud/stack-overflow-debug #308

Triggered via push March 27, 2026 10:39
Status Failure
Total duration 13m 29s
Artifacts 17

ci.yaml

on: push
Matrix: test-node-compat
Matrix: test-runtime
publish
0s
publish
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 18 warnings
Failed Test: runtime::fetch::fetch_redirects
runtime::fetch::fetch_redirects: error while executing at wasm backtrace: 0: 0x96d388 - fetch.wasm!abort 1: 0x9647f4 - fetch.wasm!std::sys::pal::wasi::helpers::abort_internal::h6ac5767e1b644f6d 2: 0x95cb32 - fetch.wasm!std::process::abort::h915eac6d11016973 3: 0x95cbae - fetch.wasm!__rustc[16f1505adc47261a]::__rust_abort 4: 0x95c962 - fetch.wasm!__rustc[16f1505adc47261a]::__rust_start_panic 5: 0x95c985 - fetch.wasm!__rustc[16f1505adc47261a]::rust_panic 6: 0x966967 - fetch.wasm!std::panicking::panic_with_hook::h3ce0fb6586d9aef9 7: 0x964cc3 - fetch.wasm!std::panicking::panic_handler::{{closure}}::h2b701c2592fa9d13 8: 0x95cc9d - fetch.wasm!std::sys::backtrace::__rust_end_short_backtrace::h736755c36d5f6f42 9: 0x95cc91 - fetch.wasm!__rustc[16f1505adc47261a]::rust_begin_unwind 10: 0x97d2b5 - fetch.wasm!core::panicking::panic_fmt::h69ffce77273aac9b 11: 0x3d5186 - fetch.wasm!fetch::internal::call_js_export_internal::{{closure}}::{{closure}}::{{closure}}::h0ee1a9e0c1ad938d 12: 0x4f83a6 - fetch.wasm!<core::pin::Pin<P> as core::future::future::Future>::poll::h70afe951c7a2b833 13: 0xebd7e - fetch.wasm!<rquickjs_core::context::async::future::WithFuture<F,R> as core::future::future::Future>::poll::h8022928e5d4ede33 14: 0x3bc606 - fetch.wasm!fetch::internal::call_js_export_internal::{{closure}}::h6a0b1fa226a7cc20 15: 0x3bc37f - fetch.wasm!fetch::internal::call_js_export::{{closure}}::hbd449c0eed8e9870 16: 0x4c2c83 - fetch.wasm!<fetch::Component as fetch::bindings::Guest>::post_with_redirect::{{closure}}::h9cf711f58d40426e 17: 0x4c2757 - fetch.wasm!<futures_concurrency::future::join::tuple::Join2<A,B> as core::future::future::Future>::poll::h2dd71e0bd9494a70 18: 0x3c751e - fetch.wasm!fetch::internal::async_exported_function::{{closure}}::hb1033908112d5d1d 19: 0x43892 - fetch.wasm!async_task::raw::RawTask<F,T,S,M>::run::h4542a0f176b3f3c0 20: 0x3f78fc - fetch.wasm!async_task::runnable::Runnable<M>::run::hc4908b1e64139e0f 21: 0x177225 - fetch.wasm!wstd::runtime::block_on::block_on::hbe5305c4f315d35c 22: 0x3c2e07 - fetch.wasm!fetch::internal::async_exported_function::hb1a7ca78cdbe3062 23: 0x4f6b99 - fetch.wasm!<fetch::Component as fetch::bindings::Guest>::post_with_redirect::hdf7bc1933573c5f9 24: 0x4b406e - fetch.wasm!fetch::bindings::_export_post_with_redirect_cabi::h1237573f59269972 25: 0x4f922f - fetch.wasm!post-with-redirect note: using the `WASMTIME_BACKTRACE_DETAILS=1` environment variable may show more debugging information: wasm trap: wasm `unreachable` instruction executed - No trace available
test-runtime (2)
Process completed with exit code 101.
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-node-compat (0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-node-compat (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-node-compat (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-node-compat (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-node-compat (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-node-compat (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-node-compat (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-other
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-node-compat (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-runtime (5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-runtime (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-runtime (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-runtime (8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-runtime (6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-runtime (7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-runtime (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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-runtime (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, useblacksmith/rust-cache@v3. 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/

Artifacts

Produced during runtime
Name Size Digest
test-node-compat-shard-0-report Expired
38.9 KB
sha256:1454023a7b237ad6b821f74f5500a6dfe7a7ac19789e22e0d1c364b0ead10ab3
test-node-compat-shard-1-report Expired
39.3 KB
sha256:ba76947616c2503b16bbec4031d0e566ae0656f662f5a536135b8cf92c5d8f26
test-node-compat-shard-2-report Expired
39.7 KB
sha256:0a13815c84d044dc33ceaefb3f7ff6b8b4f2faebb224a2e8c9abe6b12aa86731
test-node-compat-shard-3-report Expired
38.7 KB
sha256:aa4cfa5704aacfebefd55dc2cc2cb9e548fbbbf8accc1554f34d55240263059f
test-node-compat-shard-4-report Expired
38 KB
sha256:35cb7875d87d53cba0a8a64662ca9664522d86ec4dd76e17a1ae724bbdb3647c
test-node-compat-shard-5-report Expired
39.3 KB
sha256:8656b0ffa945c7e4763f39dbab3e843164299067476c845d898696a07b0186e3
test-node-compat-shard-6-report Expired
39.4 KB
sha256:ac1f651e6eb857c922d54f41a8db95cc3ed7c0fa3e396fbca4fd05aa164d276d
test-node-compat-shard-7-report Expired
40.7 KB
sha256:0ab01756a1205406e3ab705a49a0a4759dbe3498d498f13342a2f2ab1bfdc3dd
test-other-report Expired
4.21 KB
sha256:7b2ec24d880e806c6d4367d77707690aa9f814e00bdf296c7913a38213f3e438
test-runtime-group-1-report Expired
4.29 KB
sha256:ca182bae74a3f4ef14d9791d1be69b3b121536e457297ddd313926c96f0bcb08
test-runtime-group-2-report Expired
4.91 KB
sha256:22c978b650f9236dab4691f05651e90441b20042f4a831aa5cc6532c447adf92
test-runtime-group-3-report Expired
3.74 KB
sha256:3f842fa233b5aa359a4548fc646df278ff234e17bbd72b4b1a86b0e46b99fd85
test-runtime-group-4-report Expired
3.77 KB
sha256:a3eb8137aeabd46fcc5ee04f596a61d001f2de083afc784bf4c87548d778fc63
test-runtime-group-5-report Expired
3.61 KB
sha256:98ca89f4de69cc417035edfbcda6b17131a847d9fbf1106c66837d03b5941ecf
test-runtime-group-6-report Expired
4.13 KB
sha256:5b7b8c6bf2c13b1915dc7aeb7584b15d6c7fb37ca7b711f4ab168f4ad03d6b48
test-runtime-group-7-report Expired
3.69 KB
sha256:8801785eca9cbd07b767ab238a1ee1bda172db6877744bc84a40c08339da5965
test-runtime-group-8-report Expired
4.12 KB
sha256:4dd6b85f87a8f5172860b801f403d6d2af6e0448cbeb44fd8b47b2a394f46f28