[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #7163 [Stem]: test_get_network_status fails
#7163: test_get_network_status fails
--------------------+-------------------------------------------------------
Reporter: neena | Owner: neena
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: Stem | Version:
Keywords: | Parent:
Points: | Actualpoints:
--------------------+-------------------------------------------------------
Changes (by atagar):
* owner: atagar => neena
Comment:
Hmmm, I dropped write permissions so our tor instance wouldn't replace the
consensus that had an issue (chmod -w test/data/cached-*), then tested
with both v0.2.1.30 (once) and v0.2.3.16 (eight times). No luck.
I could make the test check for multiple relays which would hopefully make
it more resilient, but that feels a bit a hack. As I understand it the
cached-* files really should be a reflection of tor's perception of the
network (and hence match what it responds to GETINFO queries with).
One other thought is that maybe your tor instance is using the cached-
microdesc-consensus rather than cached-consensus (honestly I find the
behavior around microdescriptors a bit confusing). We could check the
first entry of both files.
Thoughts?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7163#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs