From 190ce100597a98253c8dc2fd6036df7efaf57cfc Mon Sep 17 00:00:00 2001 From: Esteban Foronda Date: Mon, 3 May 2021 13:06:29 -0500 Subject: [PATCH] Using osFlag to fix windows worker error Signed-off-by: Aidan Oldershaw Co-authored-by: Esteban Foronda --- fly/integration/ordering_instanced_pipelines_test.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fly/integration/ordering_instanced_pipelines_test.go b/fly/integration/ordering_instanced_pipelines_test.go index 3bd96c9f9..7de3b2151 100644 --- a/fly/integration/ordering_instanced_pipelines_test.go +++ b/fly/integration/ordering_instanced_pipelines_test.go @@ -121,7 +121,7 @@ var _ = Describe("Fly CLI", func() { <-sess.Exited Expect(sess.ExitCode()).To(Equal(1)) - Expect(sess.Err).Should(gbytes.Say("error: the required flags `-g, --group' and `-p, --pipeline' were not specified")) + Expect(sess.Err).Should(gbytes.Say("error: the required flags `" + osFlag("g", "group") + "' and `" + osFlag("p", "pipeline") + "' were not specified")) }).To(Change(func() int { return len(atcServer.ReceivedRequests()) }).By(0))