The semaphore between the watcher and the protocol is not needed.

Related to #69 (closed)

The watcher stored a queue with all subtest results reading console files. The protocol consumed that queue. That's why we used the semaphore.

Right now, the watcher is not storing any subtest results, this information is on the restraint XML file, and the protocol has a function to sync the status between the console and the restraint file (consolidate_restraint_file_and_console).

After that, the protocol uses the function use_action_rules using that semaphore.

Signed-off-by: Israel Santana Aleman isantana@redhat.com