Describe the problem/challenge you have
We do have some timestamp information when Antrea e2e have some logs codes to print useful information. but it would be better to have some high level execution time line during e2e.
Describe the solution you'd like
We may have below ways to enhance the log which can help us to analyze the timeline and do enhancement easier.
Add timestamp log information before and after each e2e case or check if go test provide such function to collect detail execution time.
Add jenkins console log timestamp which can help to understand which part will be the bottleneck during e2e env preparation. one plugin might be used https://plugins.jenkins.io/timestamper/.
Describe the problem/challenge you have We do have some timestamp information when Antrea e2e have some logs codes to print useful information. but it would be better to have some high level execution time line during e2e.
Describe the solution you'd like We may have below ways to enhance the log which can help us to analyze the timeline and do enhancement easier.
Anything else you would like to add?