Summary: PLM: resurrect PLM tests
Review request for Trac Ticket(s): 1924
Peer Reviewer(s): Mathi
Pull request to: Mathi
Affected branch(es): default
Development branch:
--------------------------------
Impacted area Impact y/n
--------------------------------
Docs n
Build system n
RPM/packaging n
Configuration files n
Startup scripts n
SAF services n
OpenSAF services n
Core libraries n
Samples n
Tests y
Other n
Comments (indicate scope for each "y" above):
---------------------------------------------
changeset 2ee7663e4dac65ae39804fcf04ded384c1452073
Author: Alex Jones <ajo...@genband.com>
Date: Thu, 21 Jul 2016 10:24:12 -0400
plm: resurrect PLM tests [#1924]
This ticket brings the PLM tests back into the build, along with some
detailed instructions on how to set it up.
Added Files:
------------
tests/plmsv/config/opensaf-plm-sim.txt
tests/plmsv/config/plm-sim-imm.xml
tests/plmsv/README
Complete diffstat:
------------------
tests/Makefile | 3 +-
tests/plmsv/README | 77 +
tests/plmsv/common/Makefile.am | 3 +-
tests/plmsv/common/plmtest.c | 18 +-
tests/plmsv/common/plmtest.h | 4 +-
tests/plmsv/config/opensaf-plm-sim.txt | 12012 ++++++++++++++++++++++
tests/plmsv/config/plm-sim-imm.xml | 226 +
tests/plmsv/plms/test_saPlmEntityGroupAdd.c | 10 +-
tests/plmsv/plms/test_saPlmEntityGroupCreate.c | 2 -
tests/plmsv/plms/test_saPlmEntityGroupRemove.c | 4 +-
tests/plmsv/plms/test_saPlmInitialize.c | 1 -
tests/plmsv/plms/test_saPlmReadinessTrack.c | 293 +-
tests/plmsv/plms/test_saPlmSelectionObjectGet.c | 2 -
13 files changed, 12539 insertions(+), 116 deletions(-)
Testing Commands:
-----------------
See new README file
Testing, Expected Results:
--------------------------
See new README file
Conditions of Submission:
-------------------------
<<HOW MANY DAYS BEFORE PUSHING, CONSENSUS ETC>>
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.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Opensaf-devel mailing list
Opensaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-devel
