Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sqlite error on random builds #336

Closed
jaredwray opened this issue May 19, 2022 · 4 comments
Closed

sqlite error on random builds #336

jaredwray opened this issue May 19, 2022 · 4 comments

Comments

@jaredwray
Copy link
Owner

We continue to see random errors on builds for sqlite3

FATAL ERROR: Error::ThrowAsJavaScriptException napi_throw
 1: 0xa3aaf0 node::Abort() [/opt/hostedtoolcache/node/14.19.2/x64/bin/node]
 2: 0x970199 node::FatalError(char const*, char const*) [/opt/hostedtoolcache/node/14.19.2/x64/bin/node]
 3: 0x9701a2  [/opt/hostedtoolcache/node/14.19.2/x64/bin/node]
 4: 0xa07ddb napi_fatal_error [/opt/hostedtoolcache/node/14.19.2/x64/bin/node]
 5: 0x7fae8ca3c3de  [/home/runner/work/keyv/keyv/node_modules/sqlite3/lib/binding/napi-v6-linux-glibc-x64/node_sqlite3.node]
 6: 0x7fae8ca3ca92 Napi::Error::ThrowAsJavaScriptException() const [/home/runner/work/keyv/keyv/node_modules/sqlite3/lib/binding/napi-v6-linux-glibc-x64/node_sqlite3.node]
 7: 0x7fae8ca3d017 Napi::Function::MakeCallback(napi_value__*, unsigned long, napi_value__* const*, napi_async_context__*) const [/home/runner/work/keyv/keyv/node_modules/sqlite3/lib/binding/napi-v6-linux-glibc-x64/node_sqlite3.node]
 8: 0x7fae8ca59e40 node_sqlite3::Statement::Work_AfterAll(napi_env__*, napi_status, void*) [/home/runner/work/keyv/keyv/node_modules/sqlite3/lib/binding/napi-v6-linux-glibc-x64/node_sqlite3.node]
 9: 0xa0a329 node::ThreadPoolWork::ScheduleWork()::{lambda(uv_work_s*, int)#2}::_FUN(uv_work_s*, int) [/opt/hostedtoolcache/node/14.19.2/x64/bin/node]
10: 0x13bc2fd  [/opt/hostedtoolcache/node/14.19.2/x64/bin/node]
11: 0x13c0a86  [/opt/hostedtoolcache/node/14.19.2/x64/bin/node]
12: 0x13d2ff4  [/opt/hostedtoolcache/node/14.19.2/x64/bin/node]
13: 0x13c13d8 uv_run [/opt/hostedtoolcache/node/14.19.2/x64/bin/node]
14: 0x9d1428 node::Environment::CleanupHandles() [/opt/hostedtoolcache/node/14.19.2/x64/bin/node]
15: 0x9d6b56 node::Environment::RunCleanup() [/opt/hostedtoolcache/node/14.19.2/x64/bin/node]
16: 0x9917f7 node::FreeEnvironment(node::Environment*) [/opt/hostedtoolcache/node/14.19.2/x64/bin/node]
17: 0xafd4af node::worker::Worker::Run() [/opt/hostedtoolcache/node/14.19.2/x64/bin/node]
18: 0xafd6f8  [/opt/hostedtoolcache/node/14.19.2/x64/bin/node]
19: 0x7fae9721e[609](https://github.com/jaredwray/keyv/runs/6500107069?check_suite_focus=true#step:6:610)  [/lib/x86_64-linux-gnu/libpthread.so.0]
20: 0x7fae97143163 clone [/lib/x86_64-linux-gnu/libc.so.6]
@jaytist
Copy link
Contributor

jaytist commented May 20, 2022

@jaredwray
Copy link
Owner Author

@alphmth thanks for the link on this. Can we move it to only use the main thread and not the worker thread on build?

@jaytist
Copy link
Contributor

jaytist commented May 20, 2022

@jaredwray any idea how can we do this? I researched and found nothing about building on main thread...

@jaredwray
Copy link
Owner Author

@alphmth - what if we just update the tests.yaml to do all the other tests and exclude sqlite and then run it as a separate command at the end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants