| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"Tinytest" is a minimalist C unit testing framework I wrote for
Libevent. It supports some generally useful features, like being able
to run separate unit tests in their own processes.
I tried to do the refactoring to change test.c as little as possible.
Thus, we mostly don't call the tinytest macros directly. Instead, the
test.h header is now a wrapper on tinytest.h to make our existing
test_foo() macros work.
The next step(s) here will be:
- To break test.c into separate files, each with its own test group.
- To look into which things we can test
- To refactor the more fiddly tests to use the tinytest macros
directly and/or run forked.
- To see about writing unit tests for things we couldn't previously
test without forking.
|
| |
|
|
|
|
| |
Try to clarify things in the comment too.
|
|
|
|
|
|
|
|
| |
A) We were considering a circuit had timed out in the special cases
where we close rendezvous circuits because the final rendezvous
circuit couldn't be built in time.
B) We were looking at the wrong timestamp_created when considering
a timeout.
|
|
|
|
| |
Based on irc discussion with arma.
|
|
|
|
|
| |
Mostly by storing the timeout as milliseconds and not seconds
internally.
|
|
|
|
| |
until mike figures out some other way to make them pass reliably
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Using CircuitBuildTimeout is prone to issues with SIGHUP, etc.
Also, shuffle the circuit build times array after loading it
in so that newer measurements don't replace chunks of
similarly timed measurements.
|
| |
|
|
|
|
|
| |
Also add code to keep creating circuits every minute until we
hit our minimum threshhold.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This code adds a new field to vote on: "params". It consists of a list of
sorted key=int pairs. The output is computed as the median of all the
integers for any key on which anybody voted.
Improved with input from Roger.
|
|
|
|
| |
i guess that means i should call them unit tests and check them in.
|
|\ |
|
| |
| |
| |
| | |
Big thanks to nickm and arma for helping me with this!
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Note that unlike subversion revision numbers, it isn't meaningful to
compare these for anything but equality. We define a sort-order anyway,
in case one of these accidentally slips into a recommended-versions
list.
|
| | |
| | |
| | |
| | | |
This adds an openssl 0.9.8 dependency. Let's see if anybody cares.
|
|\ \ \
| |/ /
|/| | |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I don't think we actually use (or plan to use) strtok_r in a reentrant
way anywhere in our code, but would be nice not to have to think about
whether we're doing it.
|
| |/ / |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| | |
Now that we require EntryStatistics to be 1 for counting connecting
clients, unit tests need to set that config option, too.
Reported by Sebastian Hahn.
|
|\ \ |
|
| | | |
|
|\ \ \
| |/ /
|/| /
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
With the last fix of task 932 (5f03d6c), client requests are only added to
the history when they happen after the start of the current history. This
conflicts with the unit tests that insert current requests first (defining
the start of the client request history) followed by requests in the past.
The fix is to insert requests in chronological order in the unit tests.
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
| |
to help track whether we received them when a relay operator claims
they got sent.
svn:r19213
|
|
|
|
| |
svn:r18761
|
|
|
|
|
|
|
|
|
|
| |
tor_sscanf() only handles %u and %s for now, which will make it
adequate to replace sscanf() for date/time/IP parsing. We want this
to prevent attackers from constructing weirdly formed descriptors,
cells, addresses, HTTP responses, etc, that validate under some
locales but not others.
svn:r18760
|
|
|
|
| |
svn:r18097
|
|
|
|
|
|
| |
REVERSE_INULL. This is what we get for bragging about being down to 0 issues.
svn:r18096
|
|
|
|
| |
svn:r18095
|
|
|
|
|
|
| |
remain, though.
svn:r17888
|
|
|
|
|
|
| |
on any platform.
svn:r17887
|
|
|
|
|
|
|
|
| |
The subversion $Id$ fields made every commit force a rebuild of
whatever file got committed. They were not actually useful for
telling the version of Tor files in the wild.
svn:r17867
|
|
|
|
|
|
| |
and has decent semantics for maskbits; and so that CMP_EXACT works right for bits==0.
svn:r17788
|
|
|
|
| |
svn:r17771
|
|
|
|
| |
svn:r17755
|