CFE ES unit test failures caused by startup sync fix

[skliper]

The startup sync fix (#71) caused some unit test failures.

This is due to the fact that the counters never get incremented as expected, since this is done by the child thread. Therefore the verification that the child thread actually started cannot be unit tested.

As an interim fix this check will be removed from the main code. This will make unit tests pass in 6.4.2. Ironically, this is making the main code slightly less robust in order to appease unit tests.

In the future a unit test "hook" function can be implemented for {{{OS_TaskCreate()}}} that imitates the counter increment so the startup verification can be but back in at that time.

[skliper]

Imported from trac issue 74. Created by jphickey on 2015-06-24T10:59:21, last modified: 2015-07-02T11:37:21

[skliper]

Trac comment by jphickey on 2015-06-24 11:13:28:

Submitted [changeset:bbbb963] on branch {{{trac-74-startup-sync-ut-fix}}} that back ports my workarounds for this specific UT issue.

NOTE - the branch is based on {{{ic-hotfix-6-4-2}}}

[skliper]

Trac comment by jphickey on 2015-07-02 11:37:21:

It was decided that this would NOT be included in 6.4.2, and the release would be published with the ES unit test "as-is".

As this originally was only a back port of a piece of a larger change set (#103) this ticket will be closed. #103 has all modifications needed to make the current development unit tests work.