Re: [opensuse-factory] New Tumbleweed snapshot 20150924 released!
Hi list, TL; DR: latest snapshot basically broke nodejs for me. I am forced to report this bug here because boo replies with 404 on attempt to file it (it shows bug form on /enter_bug.cgi alright, but replies with 404 on post_bug.cgi when I press "Submit"). Steps to reproduce: * install nodejs v4.0.0 of latest snapshot and nodejs-npm/npm (both fit well) * point * run npm install --global babel (any package name works actually) Expected: named package is installed Instead: npm (well, nodejs) terminates with SIGSEGV. Note: nodejs interpreters installed with nvm (https://github.com/creationix/nvm) are not affected by this issue. Backtrace: $ gdb /usr/bin/node usr.bin.node.core […skip copyrights…] warning: core file may not match specified executable file. [New LWP 1680] [New LWP 1688] [New LWP 1692] [New LWP 1691] [New LWP 1687] [New LWP 1681] [New LWP 1694] [New LWP 1693] [New LWP 1690] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `npm '. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000000000000000 in ?? ()
bt #0 0x0000000000000000 in ?? () #1 0x0000000000bd6996 in node::crypto::Hash::HashUpdate(v8::FunctionCallbackInfov8::Value const&) () #2 0x00000000006a006b in v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfov8::Value const&)) () #3 0x00000000006cb432 in v8::internal::MaybeHandlev8::internal::Object v8::internal::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::(anonymous namespace)::BuiltinArguments<(v8::internal::BuiltinExtraArguments)1>&) [clone .constprop.66] () #4 0x00000000006cb88e in v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) () #5 0x00002250cdb060bb in ?? () #6 0x0000098de41db889 in ?? () #7 0x00002250cdb06001 in ?? () #8 0x00007ffd76342d80 in ?? () #9 0x00007ffd76342de0 in ?? () #10 0x00002250cdcfdbe9 in ?? () #11 0x0000098de41db889 in ?? () #12 0x0000201d8da65759 in ?? () #13 0x00002d4fb6522369 in ?? () #14 0x0000246228746689 in ?? () #15 0x0000098de41db889 in ?? () #16 0x0000098de41e70e9 in ?? () #17 0x00002d4fb6530a51 in ?? () #18 0x00007ffd76342e20 in ?? () #19 0x00002250cdb19494 in ?? () #20 0x0000201d8da65759 in ?? () #21 0x00002d4fb6522369 in ?? () #22 0x0000246228746629 in ?? () #23 0x0000000100000000 in ?? () #24 0x0000098de41e70e9 in ?? () #25 0x0000000a00000000 in ?? () #26 0x00007ffd76342e70 in ?? () #27 0x00002250cdcfd59c in ?? () #28 0x00002d4fb6522369 in ?? () #29 0x0000246228746629 in ?? () #30 0x0000098de41e70e9 in ?? () #31 0x0000000000000000 in ?? ()
If it's my fault that bug can't be properly reported, I kindly ask you to copy&paste this report to BOO for me. Thank you in advance. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
UPD: please ignore that "point" item
2015-09-28 20:38 GMT+03:00 Andrei Dziahel
Hi list,
TL; DR: latest snapshot basically broke nodejs for me. I am forced to report this bug here because boo replies with 404 on attempt to file it (it shows bug form on /enter_bug.cgi alright, but replies with 404 on post_bug.cgi when I press "Submit").
Steps to reproduce: * install nodejs v4.0.0 of latest snapshot and nodejs-npm/npm (both fit well) * point * run npm install --global babel (any package name works actually)
Expected: named package is installed
Instead: npm (well, nodejs) terminates with SIGSEGV.
Note: nodejs interpreters installed with nvm (https://github.com/creationix/nvm) are not affected by this issue.
Backtrace:
$ gdb /usr/bin/node usr.bin.node.core […skip copyrights…] warning: core file may not match specified executable file. [New LWP 1680] [New LWP 1688] [New LWP 1692] [New LWP 1691] [New LWP 1687] [New LWP 1681] [New LWP 1694] [New LWP 1693] [New LWP 1690] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `npm '. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000000000000000 in ?? ()
bt #0 0x0000000000000000 in ?? () #1 0x0000000000bd6996 in node::crypto::Hash::HashUpdate(v8::FunctionCallbackInfov8::Value const&) () #2 0x00000000006a006b in v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfov8::Value const&)) () #3 0x00000000006cb432 in v8::internal::MaybeHandlev8::internal::Object v8::internal::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::(anonymous namespace)::BuiltinArguments<(v8::internal::BuiltinExtraArguments)1>&) [clone .constprop.66] () #4 0x00000000006cb88e in v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) () #5 0x00002250cdb060bb in ?? () #6 0x0000098de41db889 in ?? () #7 0x00002250cdb06001 in ?? () #8 0x00007ffd76342d80 in ?? () #9 0x00007ffd76342de0 in ?? () #10 0x00002250cdcfdbe9 in ?? () #11 0x0000098de41db889 in ?? () #12 0x0000201d8da65759 in ?? () #13 0x00002d4fb6522369 in ?? () #14 0x0000246228746689 in ?? () #15 0x0000098de41db889 in ?? () #16 0x0000098de41e70e9 in ?? () #17 0x00002d4fb6530a51 in ?? () #18 0x00007ffd76342e20 in ?? () #19 0x00002250cdb19494 in ?? () #20 0x0000201d8da65759 in ?? () #21 0x00002d4fb6522369 in ?? () #22 0x0000246228746629 in ?? () #23 0x0000000100000000 in ?? () #24 0x0000098de41e70e9 in ?? () #25 0x0000000a00000000 in ?? () #26 0x00007ffd76342e70 in ?? () #27 0x00002250cdcfd59c in ?? () #28 0x00002d4fb6522369 in ?? () #29 0x0000246228746629 in ?? () #30 0x0000098de41e70e9 in ?? () #31 0x0000000000000000 in ?? ()
If it's my fault that bug can't be properly reported, I kindly ask you to copy&paste this report to BOO for me.
Thank you in advance.
-- Regards, Andrei Dziahel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 28.09.2015 um 19:38 schrieb Andrei Dziahel:
Hi list,
TL; DR: latest snapshot basically broke nodejs for me. I am forced to report this bug here because boo replies with 404 on attempt to file it (it shows bug form on /enter_bug.cgi alright, but replies with 404 on post_bug.cgi when I press "Submit").
There is one cool way to avoid this: submit an openQA test to verify nodejs functionality Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I don't think my user is able to submit openQA tests. Actions list on,
say, https://openqa.opensuse.org/tests/86072/modules/systemsettings/steps/4
looks empty to me. Can you post a direct link to submission form?
Should I add nodejs needles to existing suite or should I create new
one? What is proper flavor to add them to (my guess is new one)?
TIA.
2015-09-29 8:22 GMT+03:00 Stephan Kulow
Am 28.09.2015 um 19:38 schrieb Andrei Dziahel:
Hi list,
TL; DR: latest snapshot basically broke nodejs for me. I am forced to report this bug here because boo replies with 404 on attempt to file it (it shows bug form on /enter_bug.cgi alright, but replies with 404 on post_bug.cgi when I press "Submit").
There is one cool way to avoid this: submit an openQA test to verify nodejs functionality
Greetings, Stephan
-- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- Regards, Andrei Dziahel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 29.09.2015 um 20:03 schrieb Andrei Dziahel:
I don't think my user is able to submit openQA tests. Actions list on, say, https://openqa.opensuse.org/tests/86072/modules/systemsettings/steps/4 looks empty to me. Can you post a direct link to submission form? Should I add nodejs needles to existing suite or should I create new one? What is proper flavor to add them to (my guess is new one)?
I Andrei, Contributing openQA tests works through github, looking similiar to https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/533 The main thing to do is figuring out what to test and how. E.g. we have tests for apache and mysql that run certain commands in the shell under the linux console. Just browse in the tests folder for inspiration and sketch something for nodejs. Fixing the details you can leave to the experts if you have the master plan - as deploying openQA locally is possible but unfortunately still quite complex. Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Andrei Dziahel -
Stephan Kulow