Skip to content
This repository has been archived by the owner on May 7, 2020. It is now read-only.

Fix OneWire bridge handler test #6160

Merged
merged 3 commits into from
Sep 6, 2018

Conversation

htreu
Copy link
Contributor

@htreu htreu commented Sep 6, 2018

Addresses occasionally failing tests, see #6153 (comment)

Signed-off-by: Henning Treu [email protected]

Signed-off-by: Henning Treu <[email protected]>
@wborn
Copy link
Contributor

wborn commented Sep 6, 2018

@J-N-K
Copy link
Contributor

J-N-K commented Sep 6, 2018

LGTM. And I agree with @wborn, the archetype should be updated, too.

Signed-off-by: Henning Treu <[email protected]>
@htreu
Copy link
Contributor Author

htreu commented Sep 6, 2018

Thanks @wborn & @J-N-K, archetype updated.

@@ -80,20 +80,22 @@ public void initialize() {
// access or similar) you should set status UNKNOWN here and then decide the real status asynchronously in the
// background.

// set the thing status to UNKNOWN temporarily and let the background task decide for the real status.
// the framework is then able to reuse the resources from the thing handler initialization.
// we set this upfront to reliably check status updste sin unit tests.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Besides this "updste sin" typo the PR looks good! 👍

Signed-off-by: Henning Treu <[email protected]>
@kaikreuzer kaikreuzer merged commit 71dfe71 into eclipse-archived:master Sep 6, 2018
@htreu htreu added this to the 0.10.0 milestone Oct 30, 2018
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.

4 participants