Summary: base: calculate timer timeouts from the time computer starts [#2248] Review request for Trac Ticket(s): 2248 Peer Reviewer(s): Ramesh, Anders W Pull request to: Zoran Affected branch(es): default(5.2) Development branch: default(5.2)
-------------------------------- Impacted area Impact y/n -------------------------------- Docs n Build system n RPM/packaging n Configuration files n Startup scripts n SAF services y OpenSAF services n Core libraries n Samples n Tests n Other n Comments (indicate scope for each "y" above): --------------------------------------------- changeset 82a6e93d9e4406a2bb0ca05c6b127d74d56ae796 Author: Zoran Milinkovic <[email protected]> Date: Tue, 24 Jan 2017 10:40:05 +0100 base: calculate timer timeouts from the time computer starts [#2248] Timers started before the timer engine thread is started are calculated from the time a computer starts. Timers started after the timer engine thread started are calculated from the time the timer engine thread started. This gap in time between these two cases when timers can be added are the reason for hanging testleap forever. The patch removes the calculation for timers when the timer engine starts, and the calculation is done from the time the computer starts. Complete diffstat: ------------------ src/base/sysf_tmr.c | 27 ++++++--------------------- 1 files changed, 6 insertions(+), 21 deletions(-) Testing Commands: ----------------- make check bin/testleap Testing, Expected Results: -------------------------- Both 'make check' and 'testleap' must succeed. Conditions of Submission: ------------------------- Ack from Ramesh and Anders W Arch Built Started Linux distro ------------------------------------------- mips n n mips64 n n x86 n n x86_64 n n powerpc n n powerpc64 n n Reviewer Checklist: ------------------- [Submitters: make sure that your review doesn't trigger any checkmarks!] Your checkin has not passed review because (see checked entries): ___ Your RR template is generally incomplete; it has too many blank entries that need proper data filled in. ___ You have failed to nominate the proper persons for review and push. ___ Your patches do not have proper short+long header ___ You have grammar/spelling in your header that is unacceptable. ___ You have exceeded a sensible line length in your headers/comments/text. ___ You have failed to put in a proper Trac Ticket # into your commits. ___ You have incorrectly put/left internal data in your comments/files (i.e. internal bug tracking tool IDs, product names etc) ___ You have not given any evidence of testing beyond basic build tests. Demonstrate some level of runtime or other sanity testing. ___ You have ^M present in some of your files. These have to be removed. ___ You have needlessly changed whitespace or added whitespace crimes like trailing spaces, or spaces before tabs. ___ You have mixed real technical changes with whitespace and other cosmetic code cleanup changes. These have to be separate commits. ___ You need to refactor your submission into logical chunks; there is too much content into a single commit. ___ You have extraneous garbage in your review (merge commits etc) ___ You have giant attachments which should never have been sent; Instead you should place your content in a public tree to be pulled. ___ You have too many commits attached to an e-mail; resend as threaded commits, or place in a public tree for a pull. ___ You have resent this content multiple times without a clear indication of what has changed between each re-send. ___ You have failed to adequately and individually address all of the comments and change requests that were proposed in the initial review. ___ You have a misconfigured ~/.hgrc file (i.e. username, email etc) ___ Your computer have a badly configured date and time; confusing the the threaded patch review. ___ Your changes affect IPC mechanism, and you don't present any results for in-service upgradability test. ___ Your changes affect user manual and documentation, your patch series do not contain the patch that updates the Doxygen manual. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
