Summary: clm: add clm tests for testing long RDN support in clm [#1906] Review request for Trac Ticket(s): 1906 Peer Reviewer(s): Mathi Pull request to: Zoran Affected branch(es): default(5.1) Development branch: default(5.1)
-------------------------------- 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 27ad8b8847e90995f47c638369b13312b37a615c Author: Zoran Milinkovic <[email protected]> Date: Fri, 26 Aug 2016 16:05:37 +0200 clm: add clm tests for testing long RDN support in clm [#1906] The patch contains tests for testing long RDN support in CLM. Long DN allowed must be allowed in IMM to pass new CLM tests. Otherwise, all tests will be skipped. A test node with CLM node name "safNode=PL-1234567890123456 78901234567890123456789012345678901234567890,safCluster=myClmCluster" must be added to the cluster to pass all tests, otherwise tests that use the test node will be skipped. Added Files: ------------ tests/clmsv/tet_ClmLongRdn.c Complete diffstat: ------------------ tests/clmsv/Makefile.am | 4 +- tests/clmsv/tet_ClmLongRdn.c | 480 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 483 insertions(+), 1 deletions(-) Testing Commands: ----------------- clmtest 11 Testing, Expected Results: -------------------------- All tests in suite 11 must pass Conditions of Submission: ------------------------- Ack from Mathi 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. ------------------------------------------------------------------------------ _______________________________________________ Opensaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensaf-devel
