Ignore reboot skips, SetUpTest and TearDownTest on the subunit report of integration tests.

[elopio]

When a test requests a reboot, all the remaining tests to run check on their set up if a reboot was requested and skip themselves. Also after the reboot, all the tests that already ran do the same check and skip themselves.
This skips must be ignored on the subunit report of the executed tests.

[elopio]

go also announces the start and end of SetUpTest and TearDownTest. I think we should also ignore them, but I'll do that tomorrow.

[niemeyer]

As a rule of thumb, errors should never be ignored. When they are, there should be a comment above the line explaining why it's being ignored. If it's hard to justify, don't ignore it. If it's boring to explain, don't ignore it either, as it's easier to check than to explain.

In this case, for example, a broken regular expression will look silently and exactly the same as an expression that did not match. If you're sure the expression always matches, then create a local helper function such as:

func matchString(pattern string, s string) bool {
        matched, err := regexp.MatchString(pattern, s)
        if err != nil {
                panic(err)
        }
        return matched
}

Same applies to all such cases below.

[elopio]

Ok, I have added this function.

[niemeyer]

The logic in this branch is going over my head since I'm not aware of the inner working of subunit, so besides the one issue I could detect it above, I'd suggest picking another review from someone that understand your package. LGTM with that.

[elopio]

Thanks for the reviews.
@fgimenez I applied your suggestions, and added the other skips. Ready for another look.

[fgimenez]

Ok, 👍