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
We should add the ability to log to crossdock.T similar to testing.T. For the normal case, that would just log to stdout, but for the crossdock test, we can wrap the testing.T into a crossdock.T, and log to the test object. This will make the tests silent except in case of failure or when we use -v.
The text was updated successfully, but these errors were encountered:
=== RUN TestCrossdock
2016/09/01 19:52:59 HEAD http://127.0.0.1:54357/
2016/09/01 19:52:59 Client is ready, beginning test...
2016/09/01 19:52:59 HEAD http://127.0.0.1:54358/
2016/09/01 19:52:59 Client is ready, beginning test...
2016/09/01 19:52:59 GET http://127.0.0.1:54358/?behavior=trace&s1name=go&s2name=go&s2transport=http&s3name=go&s3transport=http&sampled=true
We should add the ability to log to
crossdock.T
similar totesting.T
. For the normal case, that would just log to stdout, but for the crossdock test, we can wrap thetesting.T
into acrossdock.T
, and log to the test object. This will make the tests silent except in case of failure or when we use-v
.The text was updated successfully, but these errors were encountered: