On Mon, 2016-09-12 at 23:21 -0700, Eric Anholt wrote:
> Is one supposed to be used somewhere else? Is it supposed to have the
> value "1" at some point?
An earlier iteration of this test tried to verify that the label did in
fact change when you changed it. But it did this by trying to
Adam Jackson writes:
> First test does some basic API error checking, then provokes an error
> against the (implicit) thread object. There is clearly much more to
> cover here, but this at least touches all of the new entrypoints and
> verifies that it errors reasonably when
Quoting Adam Jackson (2016-09-08 10:41:30)
> First test does some basic API error checking, then provokes an error
> against the (implicit) thread object. There is clearly much more to
> cover here, but this at least touches all of the new entrypoints and
> verifies that it errors reasonably when
First test does some basic API error checking, then provokes an error
against the (implicit) thread object. There is clearly much more to
cover here, but this at least touches all of the new entrypoints and
verifies that it errors reasonably when misused.
Signed-off-by: Adam Jackson