- **status**: accepted --> assigned
- **assigned_to**: elunlen
---
** [tickets:#594] logtest fail intermittent**
**Status:** assigned
**Milestone:** future
**Created:** Mon Oct 14, 2013 10:42 AM UTC by Hans Feldt
**Last Updated:** Mon Oct 14, 2013 01:52 PM UTC
**Owner:** elunlen
logtest is not reliable and behave consistent. Reasons are:
- the initialize() and finalize() done in each test case triggers a race in LOG
server. The "MDS down" event from a previous test case deletes a client recorde
for a subsequent test case.
- No TRYAGAIN for streamOpen() and streamClose(), those operation will create
and delete IMM runtime objects thus requires IMM to be writeable.
- Burst writes, there are test cases in logtest that writes a burst of 700
records with 5 us interval between. This causes a log server in an MDS/TCP
setup to crash with an assert in MDS. To be investigated. However such test
should be done externally.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
