Closed vdice closed 8 years ago
Not able to reproduce this when running locally so unable to verify a proposed fix... keeping this open for now in case it is hit again.
The solution for this problem is to sort CLI output. Right now the SDK supports sorting, so all it will take is a PR on workflow-cli to sort the output.
Has this been done in the CLI yet?
I believe so, yes. https://github.com/deis/workflow-cli/blob/a6cd7e6a4cc73c1999e879cd3e6f6918abedf9c4/cmd/config.go#L32 seems to indicate that as such. I think we can close this one out.
Encountered the following failure during an e2e run which appears to be a case of indeterminate ordering of expected command output.
The spec as currently written expects
FOO
beforeBAR
via:Which I seems to bring with it inherent order.
Also, I believe
sess.Out.Contents()
should besess.Wait().Out.Contents()
to fully wait for the process to end, per the very last section in https://onsi.github.io/gomega/#gexec-testing-external-processes