CLI time elapsed value is negative for a failed resource #11597
Labels
area/cli
UX of using the CLI (args, output, logs)
kind/bug
Some behavior is incorrect or out of spec
resolution/duplicate
This issue is a duplicate of another issue
What happened?
I ran a
pulumi up --refresh --skip-preview
and one of the resources failed the update. The elapsed time is a negative value in this case.Steps to reproduce
Create a stack with a resource that will fail during a refresh update.
Expected Behavior
The time elapsed should be a positive number.
Actual Behavior
The absolute value is correct, but the sign is wrong.
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: