GitLab

Bitswap doesn't usually care about dialing. the underlying
network adapter can make sure of that.

We use make test as the measure of correctness.
This laxity has let bugs creep into several systems.
This commit changes our target to always run expensive
tests, unless one specifically runs `make test_short`

(we would do well to remove most if not all timing--
that's usually what makes tests take a long time.)

This is causing test failures because tests don't usually
have "/-/-" format. we can decide whether or not to allow
keys without validators, but for now removing.

cc @whyrusleeping

mocknet indeterminism screwed this test up. that's twice
it's bitten us. let's not let it do it a third time.

cc @briantigerchow omg.

TestGetFailures may just be operating very slowly, instead
of completely failing. Right now it gets caught on travis
often. not sure if its actually wrong.

this fixes a failing ipns test which didnt have
a "working" routing system

Without `-f`, `make clean` fails on machines that don't have the dir.

cc @jbenet

@jbenet @whyrusleeping

This bug (missing return) could tie up the client worker and cause
operations to come to a halt.

utp is BROKEN!! it causes tests to fail.

we shouldn't use an arbitrary timeout here. since Get
doesnt take in a context yet, we give a large upper bound.
think of an http request. we want it to go on as long as
the client requests it.

this commit adds a logger with prefixes

fix sharness test for ipfs init output

sharness: verbose output

Make sharness tests' output helpful when verbose.
This means cating certain files, or running diagnostic
commands. I used a construction like:

    test_expect_success ".go-ipfs/ has been created" '
      test -d ".go-ipfs" &&
      test -f ".go-ipfs/config" &&
      test -d ".go-ipfs/datastore" ||
      fsh ls -al .go-ipfs
    '

The `|| ...` is a diagnostic run when the preceding command
fails. `fsh` is a trivial script that echoes the args, runs
the cmd, and then also fails, making sure the test case fails.
(wouldnt want the diagnostic accidentally returning true and
making it _seem_ like the test case succeeded).

mount fixes