yarn --verbose run: fix no output timeout in CI#10788
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). vault-storybook – ./ui🔍 Inspect: https://vercel.com/hashicorp/vault-storybook/fswmik97w |
|
Closing as stale. |
|
@samsalisbury this was approved, what's the blocker to merging it instead of closing? |
|
@mladlow I figured if this was still an issue then we would have heard about it? Happy to reopen & update if there's still a need for this. |
|
OK, I just checked master and this change hasn't been made there, so I'll reopen and get this merged as it should be there really for reliability. |
49aea95 to
3a74a76
Compare
|
Just re-did the work and force-pushed as easier than merging all these months later :) |
|
Thanks! I'm pretty sure it does still fail in this way from time to time. |
…0788) (hashicorp#10790) * WIP * cieps issue Co-authored-by: Violet Hynes <violet.hynes@hashicorp.com>
…0788) (hashicorp#10791) (hashicorp#10792) * WIP * cieps issue Co-authored-by: Violet Hynes <violet.hynes@hashicorp.com>
CI kills the job after 10 mins with no output, verbose mode should output enough to prevent this timeout happening.