summaryrefslogtreecommitdiff
path: root/scripts
diff options
context:
space:
mode:
authorMike Perry <mikeperry-git@torproject.org>2019-05-15 04:58:21 +0000
committerGeorge Kadianakis <desnacked@riseup.net>2019-05-15 15:10:48 +0300
commit5f47d582d50134d9504ec8e7a912887829904c8a (patch)
tree7c9135755c6a00b7b706bcadb6600e0b03c7eb55 /scripts
parent5638d65f792393a85703342bfb14cc1a60550c18 (diff)
downloadtor-5f47d582d50134d9504ec8e7a912887829904c8a.tar.gz
tor-5f47d582d50134d9504ec8e7a912887829904c8a.zip
Practracker beatings are even more fun when they get caused mid-PR due to a github auto-rebase of a PR
Because github PRs choose the most recent origin/master at the time of the PR (and for any fixups pushed to a PR later to send to CI), there are tons of conflicts and unexpected practracker issues. This means CI can suddenly fail after fixups to a branch that pass locally. Then CI fails and we have to close and re-open the PR.
Diffstat (limited to 'scripts')
-rw-r--r--scripts/maint/practracker/exceptions.txt1
1 files changed, 1 insertions, 0 deletions
diff --git a/scripts/maint/practracker/exceptions.txt b/scripts/maint/practracker/exceptions.txt
index 24452b6158..b380d507b1 100644
--- a/scripts/maint/practracker/exceptions.txt
+++ b/scripts/maint/practracker/exceptions.txt
@@ -289,3 +289,4 @@ problem function-size /src/tools/tor-gencert.c:parse_commandline() 111
problem function-size /src/tools/tor-resolve.c:build_socks5_resolve_request() 104
problem function-size /src/tools/tor-resolve.c:do_resolve() 175
problem function-size /src/tools/tor-resolve.c:main() 112
+problem function-size /src/core/or/circuitpadding.c:circpad_machine_schedule_padding() 107