Set GIT_TRACE2_EVENT_NESTING in test-lib.sh
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 9 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | test-lib.sh: set GIT_TRACE2_EVENT_NESTINGt/ | +7 | 3 replies | |
| 2/2 | t/t*: remove custom GIT_TRACE2_EVENT_NESTINGt/ t/ t/ +2 more | +5 | 0 replies |
Reviews trailers per patch
None of the 2 patches has a Reviewed-by or Acked-by.
| Patch | Jeff King | SZEDER Gábor |
|---|---|---|
| Series | Not-Acked-By | |
| 1/2 | Helped-by | |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] Set GIT_TRACE2_EVENT_NESTING in test-lib.sh
As reported by Ævar [1] and diagnosed by Peff in a reply, the default GIT_TRACE2_EVENT_NESTING is set so low that tests that look for trace2 events can start failing due to an added trace2 region. This can even be subtle, including the fact that the progress API adds trace2 regions when in use (which can depend on the verbose output of a test script).
Thanks, -Stolee
Derrick Stolee (2):
test-lib.sh: set GIT_TRACE2_EVENT_NESTING
t/t*: remove custom GIT_TRACE2_EVENT_NESTING
t/t1092-sparse-checkout-compatibility.sh | 6 +++--- t/t4216-log-bloom.sh | 2 -- t/t5310-pack-bitmaps.sh | 2 +- t/t5705-session-id-in-capabilities.sh | 2 -- t/t7519-status-fsmonitor.sh | 2 +- t/test-lib.sh | 7 +++++++ 6 files changed, 12 insertions(+), 9 deletions(-)
base-commit: 35151cf0720460a897cde9b8039af364743240e7
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1085%2Fderrickstolee%2Ftrace2-depth-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1085/derrickstolee/trace2-depth-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1085
Signature · 1 line
gitgitgadget