Skip to content
This repository was archived by the owner on Jul 16, 2020. It is now read-only.

small fixes#1129

Merged
rbradford merged 3 commits into
ciao-project:masterfrom
tpepper:resultschan_debug
Feb 8, 2017
Merged

small fixes#1129
rbradford merged 3 commits into
ciao-project:masterfrom
tpepper:resultschan_debug

Conversation

@tpepper

@tpepper tpepper commented Feb 8, 2017

Copy link
Copy Markdown

This PR cobbles together a few small fixes based on code inspection: a misnamed variable which is less clear than it should be, a simple comment typo, and a bug in normally-not-run (due to "-short") testutil results channel timeout unit tests.

Tim Pepper added 3 commits February 8, 2017 08:49
A copy/paste mistake made for a status variable being called an error
variable.  Make it status for readability

Signed-off-by: Tim Pepper <timothy.c.pepper@linux.intel.com>
I noticed a little ghost and decided to s/bookeeping/bookkeeping ;)

Signed-off-by: Tim Pepper <timothy.c.pepper@linux.intel.com>
The channel timeout tests are leaving command/error/event/status results
on the test channels.  They need to each clean up after themselves,
otherwise the channel is pre-seeded with an event which can cause
another test to incorrectly proceed instead of waiting synchronously for
a result.

As the proverb says: Channels orchestrate; mutexes serialize.  We're
hoping for a certain amount of serialization and aren't getting it
because the orchestration is faulty when it leaves unhandled messages on
the channel.

Signed-off-by: Tim Pepper <timothy.c.pepper@linux.intel.com>
@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage increased (+0.01%) to 66.696% when pulling 25d0b41 on tpepper:resultschan_debug into d1f6cd5 on 01org:master.

1 similar comment
@coveralls

Copy link
Copy Markdown

Coverage Status

Coverage increased (+0.01%) to 66.696% when pulling 25d0b41 on tpepper:resultschan_debug into d1f6cd5 on 01org:master.

@rbradford rbradford merged commit 31c703d into ciao-project:master Feb 8, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants