Skip to content
NodeJS

Fixing segfault with explain analyze followed by not a select #238

Sign in to view logs

Fixing segfault with explain analyze followed by not a select

Fixing segfault with explain analyze followed by not a select #238

Triggered via pull request February 3, 2024 16:47
@DtenwoldeDtenwolde
opened #79
78-explain-analyze-copy-leads-to-segmentation-fault
Status Failure
Total duration 51s
Artifacts –

NodeJS.yml

on: pull_request
NodeJS
42s
NodeJS
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
NodeJS
remote error: upload-pack: not our ref da64a73967a339c079d1f1c4f7b46b6d15f0a20f
NodeJS
Fetched in submodule path 'duckdb', but it did not contain da64a73967a339c079d1f1c4f7b46b6d15f0a20f. Direct fetching of that commit failed.
NodeJS
The process '/usr/bin/git' failed with exit code 128
NodeJS
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
NodeJS
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/