UkoeHB maybe a Ctest bug?? Maratyszcza/NNPACK #120 , BhallaLab/moose-core #365

Is it reproducible ?

jeffro256[m] it doesn't happen on my machine so idk

UkoeHB: maybe you can add some extra logging to the seraphis_serialization_demo.seraphis_squashed_empty test to see why it fails?

here's what I get

[----------] 2 tests from seraphis_serialization_demo

[ RUN ] seraphis_serialization_demo.seraphis_squashed_empty

Floating point exception (core dumped)

could be divide by zero for example

that's nearly the only cause of FPE these days

divide by zero in serialization?

it's serializing an empty tx in that test

Shouldn't a divide by zero be caught and handled like a normal exception with google test ? I.e. it should just fail a specific test?

Stack trace: paste.debian.net/1257675

and looks like `num_bin_members` is 0 here: github.com/UkoeHB/monero/blob/1e167…eraphis/tx_component_types.cpp#L102

jberman[m]: oh that would do it

wonder why it works on my machine...

.merges

hey i had a question abt hostin a public node over tor. i got a synced node correctly connecting over clearnet, but when i run a torsocks command to check connection over tor it says my address cannot be resolved. did some digging around online without luck. any advice for this?

This makes me feel like my configuration may be correct, but my node-peers may be unstable? "Guard poiuty is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also but it could also mean an attack against you or potentially the guard itself. Success counts are 71/151. Use counts are 0/0. 136 circuits completed, 0 were unusable, 65 collapsed, and 106 timed out. For reference, your

timeout cutoff is 81 seconds."

s/Success counts are 71/151. Use counts are 0/0. 136 circuits completed, 0 were unusable, 65 collapsed, and 106 timed out. For reference, your timeout cutoff is 81 seconds.//

* <del>This makes me feel like my configuration may be correct, but my node-peers may be unstable? "Guard poiuty is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also but it could also mean an attack against you or potentially the guard itself."</del>

* <del>This makes me feel like my configuration may be correct, but my node-peers may be unstable? "Guard poiuty is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also but it could also mean an attack against you or potentially the guard itself."</del> I'm silly, was looking at the tor logs of me trying to connect to my node. Of course a lot of circuits were failing...

Any ideas about this error? reddit.com/r/MoneroMining/comments/…s_error_message_mean_running_latest

sech1: whatever issues they have seems unrelated

it's like you said someone sending invalid data