2.0 Workflows Estimated time bug?

workflow
2.0

#1

In 2.0 build which is part of a workflow seems to have entirely irrelevant time estimates.

This example screenshot is from a job which always takes ~10 minutes, but another job in the same workflow does take ~12s

image

Perhaps the estimates are not correctly matched by job as well as repo/branch?


#2

Thank you so much for pointing this out. It definitely seems like something we missed. I will add a bug to get it resolved.


#3