Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also orlearn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also.Learn more about diff comparisons here.
base repository:libgit2/libgit2
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base:main
Choose a base ref
Loading
...
head repository:libgit2/libgit2
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare:ethomson/benchmarks
Choose a head ref
Loading
  • 8commits
  • 58files changed
  • 1contributor

Commits on Mar 1, 2025

  1. benchmarks: rename cache benchmarks

    The default in the world is to have a disk cache; it's exceptional to_not_. Flip our naming, so that the (exceptional) `nocache` tests arecalled out explicitly.
    @ethomson
    ethomson committedMar 1, 2025
    Configuration menu
    Copy the full SHA
    8f04173View commit details
    Browse the repository at this point in the history

  2. benchmarks: introduce--admin flag for admin benchmarks

    Some benchmarks require administrative privileges, namely the ones thatblow up the disk cache. Don't run them by default, to avoid obnoxioussudo password prompts, etc. Users can specify `--admin` to run them.
    @ethomson
    ethomson committedMar 1, 2025
    Configuration menu
    Copy the full SHA
    1a514b3View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    14d5a5eView commit details
    Browse the repository at this point in the history

  4. benchmarks: create top-level benchmarks folder

    Benchmarks aren't tests; create a top-level `benchmarks` folder and move`tests/benchmarks` to `benchmarks/cli`.
    @ethomson
    ethomson committedMar 1, 2025
    Configuration menu
    Copy the full SHA
    f4cc6b9View commit details
    Browse the repository at this point in the history

  5. benchmarks: the write_text benchmarks should actually write

    The `hash-object__write_text...` benchmarks are intended to call`hash-object -w`. They should actually do so.
    @ethomson
    ethomson committedMar 1, 2025
    Configuration menu
    Copy the full SHA
    02f084bView commit details
    Browse the repository at this point in the history

  6. benchmarks: add descriptions

    Benchmark scripts now have optional descriptions that will be persistedinto the JSON output.
    @ethomson
    ethomson committedMar 1, 2025
    Configuration menu
    Copy the full SHA
    172e8ecView commit details
    Browse the repository at this point in the history

  7. test

    @ethomson
    ethomson committedMar 1, 2025
    Configuration menu
    Copy the full SHA
    8d2dbf7View commit details
    Browse the repository at this point in the history

  8. Revert "test"

    This reverts commit8d2dbf7.
    @ethomson
    ethomson committedMar 1, 2025
    Configuration menu
    Copy the full SHA
    0379f86View commit details
    Browse the repository at this point in the history
Loading
[8]ページ先頭
©2009-2025 Movatter.jp