libgit2/tests
Vicent Marti a0a1b19ab0 odb: Prioritize alternate backends
For most real use cases, repositories with alternates use them as main
object storage. Checking the alternate for objects before the main
repository should result in measurable speedups.

Because of this, we're changing the sorting algorithm to prioritize
alternates *in cases where two backends have the same priority*. This
means that the pack backend for the alternate will be checked before the
pack backend for the main repository *but* both of them will be checked
before any loose backends.
2015-10-14 20:53:01 +02:00
..
attr
blame
buf
checkout
cherrypick
clar
clone
commit
config
core Plug some leaks 2015-09-27 23:32:20 +02:00
date
describe
diff
fetchhead index, iterator, fetchhead: plug leaks 2015-06-26 19:00:33 +02:00
filter
graph
index
merge
network
notes
object
odb odb: Prioritize alternate backends 2015-10-14 20:53:01 +02:00
online
pack
path
perf
rebase
refs
remote
repo
reset
resources
revert
revwalk
stash
status
stress
submodule
threads
trace
transport
win32
clar_libgit2_timer.c
clar_libgit2_timer.h
clar_libgit2_trace.c Include stacktrace summary in memory leak output. 2015-06-29 16:39:11 -04:00
clar_libgit2_trace.h
clar_libgit2.c
clar_libgit2.h
clar.c
clar.h
generate_crlf.sh
generate.py
main.c
README.md
valgrind-supp-mac.txt

Writing Clar tests for libgit2

For information on the Clar testing framework and a detailed introduction please visit:

https://github.com/vmg/clar

  • Write your modules and tests. Use good, meaningful names.

  • Make sure you actually build the tests by setting:

      cmake -DBUILD_CLAR=ON build/
    
  • Test:

      ./build/libgit2_clar
    
  • Make sure everything is fine.

  • Send your pull request. That's it.