Upgrade to Go 1.7

[zimmski]

• Upgrades to Go 1.7
• Introduces test-throughout to test with the race detector and (new)
  with the address sanitizer if it is supported by the environment
• Cleanup of some scripts

Fixes #113

[marxriedl]

did you mean thorough?

[zimmski]

Yes, and as discussed I will rename it to "test-full" since that makes more sense anyway.

[zimmski]

done

[marxriedl]

I will just believe you on the regex

[zimmski]

The build log is proof that it is working ;-)
done

[marxriedl]

Why is there still "test-verbose"?

[zimmski]

That is and should be test-verbose. You are thinking about the rename of "test-throughout" to "test-full".

[marxriedl]

True, still atm they do the same. Please correct on what I'm currently obviously not seeing.

[zimmski]

done

[marxriedl]

test-full does as of now the same as test-verbose, since we discussed that the future command should be full, delete verbose or at least explain me why its still here

[zimmski]

"test-verbose" is just "test" but with verbose output. "test-full" adds should add additional tests, like the memory sanitizer, and later maybe integration/system tests. So I think it would be wiser to just call test-verbose in test-full, and then later activate the memory sanitzer check when it is ready. I just wanted to have a single make target for the CI and I do not want to include additional checks into test/test-verbose. Now that you mentioned it, I am also voting to remove the -race argument from test/test-verbose.

[marxriedl]

Well now I see the "-v" flag. Ok, remove the -race argument since I presume this -verbose has another purpose.
Incorporate both changes, then you may ships it.

[zimmski]

The "test-verbose" is sometimes helpful because otherwise you do not see the output of a test. So for me it makes sense to keep it. I would however do all tests in test-full with the verbose flag, since we would run that in the CI.
Does that sound good to you? Also, does the above arguments for the assembly of "test-full" and the argument against -race in test/test-verbose sound good to you?

[marxriedl]

Currently slightly confused, what do you intend to do with -verbose now?

[zimmski]

Removing the "-race" flag from "test" and "test-verbose".

[marxriedl]

"I would however do all tests in test-full with the verbose flag, since we would run that in the CI." <- if you as well do that then both will do the same and I don't see the merit of keeping them both

[zimmski]

Now we are both confused? ;-) I suggest the following:

• Remove -race from test/test-verbose
• Add test-full
  • Call test-verbose should be OK to just do -race and -v
  • Do a run with -race and -v
  • Do a run with -msan and -v
• Call test-full in the CI

That makes the normal testing process (test/test-verbose) fast, and the CI would catch everything no matter what.

[marxriedl]

Now. Yes, that sounds good.

[zimmski]

done