-
Notifications
You must be signed in to change notification settings - Fork 106
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
[bug]: Failure to run TestTaprootAssetsDaemon/multi_signature_on_all_levels
#958
Comments
The actual error you're getting seems to be: |
This includes After quickly sifting through now, the only thing that jumps out immediately is many failed to connect messages in both of the files related to btcd. |
Thanks! Yeah, there's nothing that jumps out. Can you please upload the full output of the integration test itself when you run only the multi signature test? You can trigger that alone by just running |
Nice to finally get that single run down here - thanks! Attached is that output dumped in a file. If something is taking to long to respond it seems to be the second I'm happy to help, but would need a push in the right direction. Also can provide additional details about my computer if you think it could be OS specific. Original file wasn't saved here is the dump: |
Hmm, are you running things on a very old or otherwise slow machine? It looks like it's just timing out because things take too long. It looks like just starting up the node almost takes 10 seconds... |
2020 MacBook Pro, 16 GB memory, I don't typically experience issues like that... and, currently have much less running than is typical. I also have plenty of disk space. If it is simply a matter of a deadline, do you see anyway for me to configure that to be longer? |
You can bump this value, which is causing the new address creation to time out: taproot-assets/itest/test_harness.go Line 66 in c972893
But I think something's quite wrong here.
These migrations on an empty database taking multiple seconds each is very abnormal. They each take between 2 and 30 milliseconds on my machine. Just out of curiosity, if you set this to |
It did not no, unfortunately. It looks to be the same output, which is attached. And, here is the
icase-output-sqlite-settings-change.txt For our purposes we can move past this for now, assuming it does have a sprawl effect of changes in the case its fix is important. If it is something you thing is very important, I'm happy to look into this more intensely. |
Hmm, okay, so things are slightly faster but not really fast enough. To be honest, I believe this could be an issue with your hardware. Because we have other team members that are also running on MacOS without any issues. So it can't be a general problem. Do you have another machine you could try it out to rule out something specific to your machine? |
I'm going to work with someone eventually to do that, but I appreciate your time looking in. |
One thing I'm still having a bit of a struggle understanding is who so much other success on other tests? In the even we are running just this one itest case, shouldn't the timeout be running in step with the the few tests when running the entire suite OR is there anything about this test in specific straining this MacOS weakness? Any thoughts here would be much appreciated @guggero ! |
Background
I'm failing to debug through the
TestTaprootAssetsDaemon/multi_signature_on_all_levels
but experiencing broad PASS's when debugging all of theTestTaprootAssetsDaemon
suite with the same debugging configuration and also withmake itest
/make itest-only
. Despite the PASS's, the issue I depict below does occur on other tests at least,TestTaprootAssetsDaemon/mint_fund_seal_assets
.The logs from all scenarios point out to something wrong with the HTLC Interceptor. I ensure the presence of the
routerrpc
in the case where I am using VS Code's debugger. Another suspect is a Context deadline being passed but I'm not sure why that would be happening.The error logs when running with the debug configuration are in the attached file, but align with the snippets below from other
itest
runs.TaprootAssetsDaemon_multi_signature_on_all_levels_debug_logs.txt
The error logs when running with
make itest
ormake build-itest
look like this:The same from
make itest-only
:And lastly, the error logs when running with
make itest-only
and commenting out all other test cases in (test_list_on_test.go
):The debugging config is specific to VS Code, however, it intends to capture the flags that the
Makefile
andmake/testing_flags.mk
:Environment
The results above are from the latest commit of main
Please see debug config above as well.
Steps to reproduce
make install
make build itest
make
steps onlymake itest
and examine output forTestTaprootAssetsDaemon/
make itest-only
and examine output forTestTaprootAssetDaemon/
Expected behavior
Passing test.
Actual behavior
Failing test.
The text was updated successfully, but these errors were encountered: