Skip to content

Update watchdog tests -- allow shorter timeouts #6709

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

fkjagodzinski
Copy link
Member

Description

Added a mechanism which will prevent an initialised watchdog from resetting the device during final greentea communication.

This change lowers the minimal testable timeout value from 500 ms to 50 ms, which is necessary to test all the partners' boards, as some of them only support timeout values up to 150 ms.

Pull request type

[ ] Fix
[ ] Refactor
[ ] New target
[X] Feature
[ ] Breaking change

CC @scartmell-arm @jamesbeyond @0xc0170 @bulislaw

@0xc0170 0xc0170 requested review from a user and jamesbeyond April 23, 2018 15:49
Copy link
Contributor

@jamesbeyond jamesbeyond left a comment

Choose a reason for hiding this comment

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

look good to me

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 26, 2018

/morph build

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 26, 2018

@fkjagodzinski There is a build failure in the jenkins CI, please can you review? When was this branch rebased the last time? Or did you define that config anywhere in this branch?

@mbed-ci
Copy link

mbed-ci commented Apr 26, 2018

Build : SUCCESS

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

Triggering tests

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

@fkjagodzinski
Copy link
Member Author

fkjagodzinski commented Apr 26, 2018

@fkjagodzinski There is a build failure in the jenkins CI, please can you review? When was this branch rebased the last time? Or did you define that config anywhere in this branch?

@0xc0170 I don't understand the cause of this failure. The only two files this PR changes are:

$ git diff upstream/feature-watchdog origin/test_update-feature-watchdog --name-only
TESTS/mbed_drivers/watchdog/main.cpp
TESTS/mbed_hal/watchdog/main.cpp

@mbed-ci
Copy link

mbed-ci commented Apr 26, 2018

@mbed-ci
Copy link

mbed-ci commented Apr 27, 2018

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 27, 2018

@scartmell-arm When was the destination branch rebased teh last time? Can you please rebase and we rerun tests?

@0xc0170 0xc0170 force-pushed the feature-watchdog branch from 64dbd53 to 29d6dca Compare May 4, 2018 18:02
@fkjagodzinski fkjagodzinski force-pushed the test_update-feature-watchdog branch from 58bebab to d856248 Compare May 7, 2018 08:29
@fkjagodzinski
Copy link
Member Author

Rebased to current feature-watchdog, 29d6dca.

@cmonr
Copy link
Contributor

cmonr commented May 7, 2018

/morph build

@mbed-ci
Copy link

mbed-ci commented May 7, 2018

Build : SUCCESS

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

Triggering tests

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

@mbed-ci
Copy link

mbed-ci commented May 7, 2018

@mbed-ci
Copy link

mbed-ci commented May 7, 2018

@fkjagodzinski
Copy link
Member Author

I updated the default timeout value used in several tests to 100 ms:

  • tests-mbed_drivers-watchdog,
  • tests-mbed_drivers-watchdog_reset,
  • tests-mbed_hal-watchdog,
  • tests-mbed_hal-watchdog_reset.

Regarding the tests-mbed_hal-watchdog_timing, I'll update this test in a separate PR according to @scartmell-arm suggestion.

@fkjagodzinski
Copy link
Member Author

@scartmell-arm, I consider this PR ready, unless you have some comments, of course. As I mentioned above I'll prepare another one for the timing test.

@cmonr
Copy link
Contributor

cmonr commented May 21, 2018

@scartmell-arm ?

@cmonr
Copy link
Contributor

cmonr commented May 21, 2018

/morph build

@mbed-ci
Copy link

mbed-ci commented May 22, 2018

Build : FAILURE

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

@fkjagodzinski
Copy link
Member Author

For several targets the IAR linker fails to process mbed-os-example-lorawan. @0xc0170, @cmonr How can we fix this, should the feature branch be rebased?

@0xc0170
Copy link
Contributor

0xc0170 commented May 22, 2018

@fkjagodzinski I noticed this error on another feature branch. yes, needs to be rebased to get the fix in.

@scartmell-arm Can you please rebase?

@0xc0170 0xc0170 force-pushed the feature-watchdog branch from 29d6dca to 2b01e51 Compare May 22, 2018 11:10
@0xc0170
Copy link
Contributor

0xc0170 commented May 22, 2018

@fkjagodzinski The feature branch was rebased, this needs now resolving the conflicts

Added a mechanism which will prevent an initialised watchdog from
resetting the device during final greentea communication.
This allows testing watchdog timeouts as short as 50 ms.
@fkjagodzinski fkjagodzinski force-pushed the test_update-feature-watchdog branch from e5b67f6 to 1ef4621 Compare May 22, 2018 12:31
@fkjagodzinski
Copy link
Member Author

Rebased to current feature-watchdog, 2b01e51.

@0xc0170
Copy link
Contributor

0xc0170 commented May 22, 2018

/morph build

@mbed-ci
Copy link

mbed-ci commented May 22, 2018

Build : SUCCESS

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

Triggering tests

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

@mbed-ci
Copy link

mbed-ci commented May 22, 2018

@mbed-ci
Copy link

mbed-ci commented May 22, 2018

@cmonr cmonr merged commit a471244 into ARMmbed:feature-watchdog May 22, 2018
@fkjagodzinski fkjagodzinski deleted the test_update-feature-watchdog branch May 25, 2018 10:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants