Details
- Reviewers
sammccall - Commits
- rG10c8dbcb840c: [clangd] Propogate context in TUScheduler::run
Diff Detail
- Repository
- rG LLVM Github Monorepo
Unit Tests
Time | Test | |
---|---|---|
50 ms | LLVM.tools/llvm-ar::Unknown Unit Message ("") |
Event Timeline
Build result: fail - 59544 tests passed, 1 failed and 805 were skipped.
failed: LLVM.tools/llvm-ar/mri-utf8.test
Log files: cmake-log.txt, ninja_check_all-log.txt, CMakeCache.txt
I am moving it into the lambda, which should extend the lifespan of context until destruction of it. Why would I need to set it in addition to that?
clang-tools-extra/clangd/TUScheduler.cpp | ||
---|---|---|
925 | Maybe inline ActionWithCtx? This should look fine as the last argument of the function call. |
Because we don't just want the context to be alive, it should be the context associated with the current thread.
e.g. if a new span is created, it should be nested within the other context.
Build result: fail - 59544 tests passed, 1 failed and 805 were skipped.
failed: LLVM.tools/llvm-ar/mri-utf8.test
Log files: cmake-log.txt, ninja_check_all-log.txt, CMakeCache.txt
Build result: fail - 59544 tests passed, 1 failed and 805 were skipped.
failed: LLVM.tools/llvm-ar/mri-utf8.test
Log files: cmake-log.txt, ninja_check_all-log.txt, CMakeCache.txt
Maybe inline ActionWithCtx? This should look fine as the last argument of the function call.