Skip to content

Conversation

maciejbocianski
Copy link
Contributor

Description

New test suite for Thread signals

Status

READY

@0xc0170
Copy link
Contributor

0xc0170 commented Sep 19, 2017

cc @bulislaw @c1728p9

Copy link
Contributor

Choose a reason for hiding this comment

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

Is this an old comment?

Copy link
Contributor

Choose a reason for hiding this comment

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

What does this comment mean?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

X. - indicates subtest number
X.1, X.2, ... - indicates subtest flow

Copy link
Contributor Author

Choose a reason for hiding this comment

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

comment added

Copy link
Member

@bulislaw bulislaw left a comment

Choose a reason for hiding this comment

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

Could you make sure the tests are small, actual unit tests. And that the description are clear and accurate please.

Copy link
Member

Choose a reason for hiding this comment

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

Can we not have such long tests? I think having to number and subnumber the flows means it's too complicated. Could we redesign it? Maybe split it up in separate test cases and use templates.

Copy link
Member

Choose a reason for hiding this comment

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

Can you rewrite the description to be a bit more grammatically correct please.

Copy link
Member

Choose a reason for hiding this comment

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

I can clearly see two test cases here (template?).

Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure what that does reading the description.

Copy link
Member

Choose a reason for hiding this comment

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

I thin that should be rewritten to closer match the test case, something like:
Given two threads A and B
When thread A waits for a signal
and thread B calls @A signal_set
Then thread A wakes up and receives correct signal

@0xc0170
Copy link
Contributor

0xc0170 commented Sep 28, 2017

@maciejbocianski please look at the latest review comments

@maciejbocianski
Copy link
Contributor Author

@0xc0170 @bulislaw done

Copy link
Member

Choose a reason for hiding this comment

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

typo wiat -> wait

Copy link
Member

Choose a reason for hiding this comment

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

Why don't we assert correct status here? But we pass it back to main thread?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I assumed that asserting in main function will make it easier to analyze the tests

Copy link
Member

Choose a reason for hiding this comment

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

I think it works both ways, with 'where did that value came from' factor. @0xc0170 any preferences from your side?

Copy link
Contributor

Choose a reason for hiding this comment

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

My preference would be the failure as soon as it happens (in this scope in this case)

Copy link
Member

Choose a reason for hiding this comment

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

can we make the names a bit more readable? eg signal_release_wait_release or something more abstract even

Copy link
Member

Choose a reason for hiding this comment

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

When thread A calls -> and similar for all of the descriptions

Copy link
Member

Choose a reason for hiding this comment

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

is running or one running thread -> and something similar for other descriptions

Copy link
Member

Choose a reason for hiding this comment

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

Could the first line for all test document, on a high level, what the tests asserts? Something like "Validate that set signals accumulate and cause signal wait to return"

Copy link
Member

Choose a reason for hiding this comment

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

Maybe we could also validate that:

  • we can set a signal then clear or wait and then set it again
  • what happens when we set the same signal twice

Copy link
Member

Choose a reason for hiding this comment

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

wiat -> wait

Copy link
Member

Choose a reason for hiding this comment

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

wiat -> wait

Copy link
Member

Choose a reason for hiding this comment

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

I don't like 0 in names, can we have some more readable names please

@maciejbocianski maciejbocianski force-pushed the signal_tests branch 2 times, most recently from de8f98d to 1b3b1ce Compare October 2, 2017 12:45
@theotherjimmy
Copy link
Contributor

@bulislaw Could you review again?

@mbed-ci
Copy link

mbed-ci commented Oct 16, 2017

Build : SUCCESS

Build number : 178
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5123/

Skipping test trigger, missing label 'NEED CI'

@0xc0170
Copy link
Contributor

0xc0170 commented Oct 19, 2017

/morph test

@0xc0170
Copy link
Contributor

0xc0170 commented Oct 19, 2017

/morph uvisor-test

@mbed-ci
Copy link

mbed-ci commented Oct 19, 2017

@maciejbocianski maciejbocianski force-pushed the signal_tests branch 2 times, most recently from 27d73ae to 37e6eee Compare October 24, 2017 13:22
@adbridge
Copy link
Contributor

Failing test:
tests-mbedmicro-rtos-mbed-signals Validate that call signal_set with prohibited signal doesn't change thread signals

@bulislaw
Copy link
Member

/morph build

@mbed-ci
Copy link

mbed-ci commented Oct 27, 2017

Build : SUCCESS

Build number : 357
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5123/

Triggering tests

/morph test
/morph uvisor-test

@mbed-ci
Copy link

mbed-ci commented Oct 27, 2017

@maciejbocianski
Copy link
Contributor Author

@mprse could you look on lptimer fail in test tests-mbed_drivers-lp_timer

>>> Running case #2: 'Test: LowPowerTimer - measure time accumulation.'...
[CONN][RXD] :184::FAIL: Values Not Within Delta 1 Expected 1060 Was 1058

@maciejbocianski
Copy link
Contributor Author

could we rerun morph ?

@mprse
Copy link
Contributor

mprse commented Nov 3, 2017

@mprse could you look on lptimer fail in test tests-mbed_drivers-lp_timer

Patch for ticker test can be found here: #5403.

@0xc0170
Copy link
Contributor

0xc0170 commented Nov 13, 2017

/morph build

@mbed-ci
Copy link

mbed-ci commented Nov 13, 2017

Build : SUCCESS

Build number : 497
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5123/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

@mbed-ci
Copy link

mbed-ci commented Nov 13, 2017

@studavekar
Copy link
Contributor

/morph test

@mbed-ci
Copy link

mbed-ci commented Nov 13, 2017

@maciejbocianski
Copy link
Contributor Author

maciejbocianski commented Nov 17, 2017

Patch for ticker test can be found here: #5403.

#5403 was merged, can proceed

@0xc0170
Copy link
Contributor

0xc0170 commented Nov 17, 2017

Lets retest

/morph build

@mbed-ci
Copy link

mbed-ci commented Nov 17, 2017

Build : SUCCESS

Build number : 545
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5123/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

@mbed-ci
Copy link

mbed-ci commented Nov 17, 2017

@mbed-ci
Copy link

mbed-ci commented Nov 17, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants