--- Log opened Thu Sep 16 00:00:09 2021 00:28 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 268 seconds] 05:35 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 06:29 -!- robert__ [uid518342@id-518342.tinside.irccloud.com] has joined #c-lightning 06:31 < robert__> Did I actually make it here? 06:33 < vincenzopalazzo> robert__: What? 06:33 < robert__> LOL after a million attempts I am finally on IRC... wow 06:35 < vincenzopalazzo> Ah! Hello ✌️ 06:36 < robert__> Did you have any idea on why my tests are failing? I mean, if the first test (test_closing) passes, shouldn't the rest? Doesn't that mean bitcoind is happy enough? 06:36 < vincenzopalazzo> robert__: Can you share the error= 06:36 < vincenzopalazzo> ? 06:37 < robert__> I'm referring to the one in my pull request, but I can paste it again here 06:37 < vincenzopalazzo> because it was not in your system 06:37 < vincenzopalazzo> on the PR it was failing the bitcoind 06:40 < robert__> It's installed tho: /usr/local/bin/bitcoind 06:41 < vincenzopalazzo> ok if you ran now the make pytest can past the error? 06:42 < robert__> It's all there in the PR. This was a fresh clone and make && make install and all the good stuff to run make pytests. simple procedure on a fresh install 06:42 < robert__> Therefore I'm asking for help... because it should just work 06:43 < robert__> ok, trying again and now I get make: *** [tools/Makefile:16: tools/headerversions] Error 1 06:44 < robert__> not sure what messed it up 06:45 < vincenzopalazzo> before all you don't need to run sudo make install because you are installing the dev version on the system. Well you can but what it the meaning? 06:46 < vincenzopalazzo> robert__: Can push all the error?, error 1 it is returned by the Makefile usually 06:47 < robert__> ~/src/lightning$ make 06:47 < robert__> CC: cc -DBINTOPKGLIBEXECDIR="../libexec/c-lightning" -Wall -Wundef -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wold-style-definition -Werror -std=gnu11 -g -fstack-protector-strong -I ccan -I external/libwally-core/include/ -I external/libwally-core/src/secp256k1/include/ -I external/jsmn/ -I external/libbacktrace/ -I external/gheap/ -I external/x86_64-linux-gnu/libbacktrace-build -I . -I/usr/local/include 06:47 < robert__> -I/usr/include/postgresql -DCCAN_TAKE_DEBUG=1 -DCCAN_TAL_DEBUG=1 -DCCAN_JSON_OUT_DEBUG=1 -DSHACHAIN_BITS=48 -DJSMN_PARENT_LINKS -DCOMPAT_V052=1 -DCOMPAT_V060=1 -DCOMPAT_V061=1 -DCOMPAT_V062=1 -DCOMPAT_V070=1 -DCOMPAT_V072=1 -DCOMPAT_V073=1 -DCOMPAT_V080=1 -DCOMPAT_V081=1 -DCOMPAT_V082=1 -DCOMPAT_V090=1 -DCOMPAT_V0100=1 -DBUILD_ELEMENTS=1 -c -o 06:47 < robert__> LD: cc config.vars -Lexternal/x86_64-linux-gnu -lwallycore -lsecp256k1 -ljsmn -lbacktrace -L/usr/local/lib -lm -lgmp -lsqlite3 -lz -L/usr/lib/x86_64-linux-gnu -lpq -lsodium -o 06:47 < robert__> collect2: error: ld returned 1 exit status 06:47 < robert__> make: *** [tools/Makefile:16: tools/headerversions] Error 1 06:47 < robert__> ~/src/lightning$ 06:47 < robert__> At the moment make is always getting stuck on that 06:47 < robert__> This is new to me... I didn't see this earlier 06:50 < vincenzopalazzo> can put on https://pastebin.com/ all the result of your ./configure --enable-developer 06:51 < robert__> ok, I'll have to run ./configure --enable-developer again because it long since scrolled away.. moment 06:52 < robert__> Oops: found the root of ALL life's problems just now....... 06:52 < robert__> "No space left on device" 07:01 -!- darosior [~darosior@194.36.189.246] has quit [Read error: Connection reset by peer] 07:02 -!- darosior [~darosior@194.36.189.246] has joined #c-lightning 07:31 -!- sturles [~sturles@sauron.uio.no] has joined #c-lightning 09:42 -!- xenonfun[m] [~xenonfunm@2001:470:69fc:105::f992] has joined #c-lightning 09:52 -!- sandipndev [sandipndev@2600:3c00::f03c:92ff:fe8e:dce6] has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in] 09:52 -!- yakshaver [yakshaver@2600:3c00::f03c:92ff:fe8e:dce6] has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in] 09:53 -!- yakshaver [~yakshaver@shindig.notmandatory.org] has joined #c-lightning 09:54 -!- sandipndev [sandipndev@2600:3c00::f03c:92ff:fe8e:dce6] has joined #c-lightning 10:27 -!- sandipndev [sandipndev@2600:3c00::f03c:92ff:fe8e:dce6] has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in] 10:27 -!- yakshaver [~yakshaver@shindig.notmandatory.org] has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in] 10:31 -!- yakshaver [yakshaver@2600:3c00::f03c:92ff:fe8e:dce6] has joined #c-lightning 10:31 -!- sandipndev [sandipndev@2600:3c00::f03c:92ff:fe8e:dce6] has joined #c-lightning 10:51 -!- _aj_ [aj@cerulean.erisian.com.au] has quit [Quit: Lost terminal] 11:08 < robert__> Ok, that was fun. Now I'm back with a bigger disk and a fresh c-lightning build, and a new error. 11:10 < robert__> https://pastebin.com/8U9WfyLh 11:11 < robert__> Does anyone recognize that or have a clue what I might have overlooked in the setup? (I was able to successfully run start_ln.) 11:32 < vincenzopalazzo> "https://pastebin.com/8U9WfyLh" <- pip3 install -r requirements.txt 11:33 < robert__> Wow, how did I miss that, thanks 11:49 < robert__> Ok, after installing that and trying again, I am back to the same issues as before with the tests failing 11:50 < vincenzopalazzo> what issue? can you share all the stack trace? 11:50 < vincenzopalazzo> ah wait 11:50 < vincenzopalazzo> if you have on a fresh machine install all the dependeces https://lightning.readthedocs.io/INSTALL.html#to-build-on-ubuntu 11:51 < robert__> Yes, I did install those. 11:51 < vincenzopalazzo> ok, if you copy and mast all the stack trace that you receive I will try to help 11:51 < vincenzopalazzo> but I need all the stacktrace 11:53 < robert__> Ok, I am doing it again and redirecting it to a file this time, not to lose anything 11:53 < vincenzopalazzo> yep 11:58 < robert__> https://pastebin.com/HjvC5R6f 12:00 < robert__> This time test_closing passed, but it does not always. The results seem to be inconsistent, but so far I haven't gotten past the closing_XXX tests. 12:00 < vincenzopalazzo> it is not anymore a bitcoind error 12:01 < robert__> Correct... it seems to be inconsistent what error comes. 12:03 < vincenzopalazzo> make VALGRIND=0 pytest 12:03 -!- aj_ [aj@cerulean.erisian.com.au] has joined #c-lightning 12:03 -!- aj_ [aj@cerulean.erisian.com.au] has quit [Changing host] 12:03 -!- aj_ [aj@user/aj/x-5857768] has joined #c-lightning 12:03 < vincenzopalazzo> ps: It looks like that you have some memory leeks somewhere, but unable to catch where 12:03 -!- aj_ is now known as _aj_ 12:05 < robert__> This has no code changes applied... it is a fresh clone! 12:06 < vincenzopalazzo> well there is some issue with some memleak opened. However, make VALGRIND=0 pytest should work 12:06 < robert__> Trying at the moment... 12:07 < vincenzopalazzo> ps: The test workflow it is complex, some may fails it is not a big deal in local. Usually some protocol test fails, but it is normal in local 12:08 < vincenzopalazzo> So I suggest to run only your test, also because run all the test each time take time. I share some command with you somewhere yet 12:08 < robert__> If that is the case, shouldn't the tests continue? I mean, why stop the whole chain if some occasional failures are expected? 12:08 < vincenzopalazzo> already not yet* 12:08 < robert__> Yes, I have the command 12:09 < robert__> Please can you enlighten me on how you recognized VALGRIND as the culprit in this error? 12:10 < vincenzopalazzo> used that, and run all the test on github action. The workflow imo it is well done, and you can get all the future failure from github. In local, run only what you need to test to make sure that you are not missing nothings 12:11 < robert__> Ok, I understand what you are saying. I am happy to save that time. 12:17 < vincenzopalazzo> "Please can you enlighten me on..." <- well I'm not the right people, because I'm not a reader person, but in the make information there is at line 66 of your pastbin the valgrid command is run. 12:17 < vincenzopalazzo> Maybe it is not a memleak, but it is a timeout error. You can find all the info in the log file that send me 12:18 < vincenzopalazzo> yep I confirm that it is a timeout error 12:18 < robert__> Ok, yes, I saw the timeout. 15:27 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning 15:37 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 252 seconds] 15:50 -!- Centurion_Dan [~Thunderbi@crm.2serve.nz] has quit [Remote host closed the connection] 15:51 -!- Centurion_Dan [~Thunderbi@crm.2serve.nz] has joined #c-lightning 15:51 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 16:37 -!- rusty [~rusty@pa49-178-13-131.pa.nsw.optusnet.com.au] has joined #c-lightning 17:17 -!- belcher_ [~belcher@user/belcher] has joined #c-lightning 17:20 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 240 seconds] 17:21 -!- Ademan [~ademan@47.185.115.221] has joined #c-lightning 17:23 -!- Dan[m]12 [~drobertsm@2001:470:69fc:105::c80] has joined #c-lightning 17:25 -!- Ademan [~ademan@47.185.115.221] has quit [Client Quit] 18:14 -!- rusty [~rusty@pa49-178-13-131.pa.nsw.optusnet.com.au] has quit [Ping timeout: 268 seconds] 18:58 -!- rusty [~rusty@203.221.41.134] has joined #c-lightning 20:08 -!- Centurion_Dan [~Thunderbi@crm.2serve.nz] has quit [Remote host closed the connection] 20:08 -!- Centurion_Dan [~Thunderbi@crm.2serve.nz] has joined #c-lightning 20:18 -!- Centurion_Dan [~Thunderbi@crm.2serve.nz] has quit [Remote host closed the connection] 20:18 -!- Centurion_Dan [~Thunderbi@crm.2serve.nz] has joined #c-lightning 21:21 -!- rusty [~rusty@203.221.41.134] has quit [Ping timeout: 265 seconds] 22:12 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning 22:41 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 265 seconds] 22:43 -!- Victorsueca [~Victorsue@90.165.120.190] has joined #c-lightning --- Log closed Fri Sep 17 00:00:10 2021