Closed huaiyan closed 1 week ago
12 files 12 suites 7m 47s :stopwatch: 19 tests 19 :white_check_mark: 0 :zzz: 0 :x: 228 runs 228 :white_check_mark: 0 :zzz: 0 :x:
Results for commit 8768e80b.
:recycle: This comment has been updated with latest results.
4 files 4 suites 4m 5s :stopwatch: 238 tests 203 :white_check_mark: 35 :zzz: 0 :x: 952 runs 812 :white_check_mark: 140 :zzz: 0 :x:
Results for commit f6790072.
:recycle: This comment has been updated with latest results.
0 tests 0 :white_check_mark: 0s :stopwatch: 0 suites 0 :zzz: 0 files 0 :x:
Results for commit f6790072.
:recycle: This comment has been updated with latest results.
6 tests 6 :white_check_mark: 1m 18s :stopwatch: 1 suites 0 :zzz: 1 files 0 :x:
Results for commit f6790072.
:recycle: This comment has been updated with latest results.
792 tests 792 :white_check_mark: 3m 44s :stopwatch: 1 suites 0 :zzz: 1 files 0 :x:
Results for commit f6790072.
:recycle: This comment has been updated with latest results.
242 tests 237 :white_check_mark: 5m 10s :stopwatch: 1 suites 5 :zzz: 1 files 0 :x:
Results for commit f6790072.
:recycle: This comment has been updated with latest results.
4 files 4 suites 59m 21s :stopwatch: 668 tests 655 :white_check_mark: 13 :zzz: 0 :x: 2 672 runs 2 620 :white_check_mark: 52 :zzz: 0 :x:
Results for commit f6790072.
:recycle: This comment has been updated with latest results.
Description
Add util method to summarize trace count telemetry.
For long term telemetry, we will need span count. The simplest solution is create custom event for each trace id and include span count in custom dimension. But that may generate too many customer events to affect all telemetry. So, we only record trace count first, and decide how to add span count later according to trace count's telemetry. Maybe just decide a reasonable sampling rate.
All Promptflow Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines