When the XRay user calls the API to finish writing the log, the thread
which is calling the API still hasn't finished and therefore won't get
its trace written. Add a test for only the main thread to check this.
Details
Details
Diff Detail
Diff Detail
- Build Status
Buildable 10769 Build 10769: arc lint + arc unit
Event Timeline
Comment Actions
break up RUN: lines in the test
lib/xray/xray_fdr_logging.cc | ||
---|---|---|
119–127 | That write will only be triggered if the second member of the tuple is true, which may or may not be the case. Hence the explicit write in an "if this thread needs it". (Your question makes sense and I had it like that at first. It didn't work, though.) | |
test/xray/TestCases/Linux/fdr-single-thread.cc | ||
2 | I've also removed the "TRACE" thing when there's a perfectly sensible default. |
Shouldn't this happen before we write out the data instead, so we don't need to do a special write here?