diff options
| author | Anton Afanasyev <anton.a.afanasyev@gmail.com> | 2021-08-26 01:32:39 +0300 |
|---|---|---|
| committer | Anton Afanasyev <anton.a.afanasyev@gmail.com> | 2021-09-01 09:11:36 +0300 |
| commit | ff780014b29617c54493a21e3a05cac35e448026 (patch) | |
| tree | 13c466dfcdd013289d1101c2c2a7bb3eb21568ad /clang/lib/Interpreter/Interpreter.cpp | |
| parent | 01152626ab87c6a9e76207a4a77b86a8a4ce6bbd (diff) | |
| download | llvm-ff780014b29617c54493a21e3a05cac35e448026.zip llvm-ff780014b29617c54493a21e3a05cac35e448026.tar.gz llvm-ff780014b29617c54493a21e3a05cac35e448026.tar.bz2 | |
[Test][Time profiler] Fix test time checking
This test sometimes triggers failures during build testing. For instance, see:
https://lab.llvm.org/buildbot/#/builders/52/builds/10161, details: https://lab.llvm.org/buildbot/#/builders/52/builds/10161/steps/5/logs/FAIL__Clang__check-time-trace-sections_cpp .
AFAICT the time between driver calling and checking its time tracker output
is not guaranteed to be stable and small:
```
> head -2 check-time-trace-sections.cpp
// RUN: %clangxx -S -ftime-trace -ftime-trace-granularity=0 -o %T/check-time-trace-sections %s
// RUN: cat %T/check-time-trace-sections.json | %python %S/check-time-trace-sections.py
> clang -S -ftime-trace -ftime-trace-granularity=0 -o /tmp/check check-time-trace-sections.cpp
> cat /tmp/check.json | python check-time-trace-sections.py
> sleep 10
> cat /tmp/check.json | python check-time-trace-sections.py
'beginningOfTime' should represent the absolute time when the process has started
>
```
The attribute `beginningOfTime` was introduced here: https://reviews.llvm.org/D78030
One can change "10 sec" value to something longer, but I believe
it's enough just to check that `beginningOfTime` exists and is
not later than current time.
Differential Revision: https://reviews.llvm.org/D108625
Diffstat (limited to 'clang/lib/Interpreter/Interpreter.cpp')
0 files changed, 0 insertions, 0 deletions