You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OK so there was a check for an exit code of 1 during in our test.sh script - but the test was failing with exit code 2! I've fixed this, and confirmed that a broken test (which in this case we had) would fail the build.
On Fri, Nov 1, 2019 at 4:43 AM Matt Fellows ***@***.***> wrote:
OK so there was a check for an exit code of 1 during in our test.sh
script - but the test was failing with exit code 2! I've fixed this, and
confirmed that a broken test (which in this case we had) would fail the
build.
1.0.4 out the door.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#121?email_source=notifications&email_token=AAAIGFIUDB6SMDG6PFULEUTQRQI5NA5CNFSM4JHQRZR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC2WRJA#issuecomment-548759716>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAIGFJM5EDQVIU45PRFXLLQRQI5NANCNFSM4JHQRZRQ>
.
Software versions
Expected behaviour
successful build
Actual behaviour
failed to build
94da099#diff-2a840891922e12f5e3573f1d11373d6eR64 includes a reference to the
os
package but does not include the import statement.Steps to reproduce
build package
Relevent log files
github.com/pact-foundation/pact-go/dsl/publish.go:64:14: undefined: os
The text was updated successfully, but these errors were encountered: