Skip to content

csp/os_process.py and csp/os_thread.py not exhibiting same behaviour #15

@snim2

Description

@snim2

From old Google Code repo:

See test/test_builtins.py

Run all tests with set_debug(True) turned on. It looks like a reader starts before a writer and the reader does not unblock after _available has been released:

DEBUG:root:3 processes in Par:
DEBUG:root:+++ Write on Channel 4b34defc-99e8-11df-a19b-002421449824 started.
DEBUG:root:++++ Writer on Channel 4b34defc-99e8-11df-a19b-002421449824: _available: 1 _taken: 0. 
DEBUG:root:+++ Read on Channel 4b3561c4-99e8-11df-a19b-002421449824 started.
DEBUG:root:++++ Reader on Channel 4b3561c4-99e8-11df-a19b-002421449824: _available: 0 _taken: 0. 
DEBUG:root:+++ Read on Channel 4b34defc-99e8-11df-a19b-002421449824 started.
DEBUG:root:++++ Reader on Channel 4b34defc-99e8-11df-a19b-002421449824: _available: 1 _taken: 0. 
DEBUG:root:+++ Read on Channel 4b34defc-99e8-11df-a19b-002421449824 finished.
DEBUG:root:+++ Write on Channel 4b3561c4-99e8-11df-a19b-002421449824 started.
DEBUG:root:++++ Writer on Channel 4b3561c4-99e8-11df-a19b-002421449824: _available: 1 _taken: 0. 

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions