The "g_main_context_check" interface ignores it's "max_priority" parameter
Submitted by Areg Beketovski
Link to original bug (#477659)
Description
Please describe the problem: Documentation states that "max_priority" input parameter of the interface g_main_context_check determines "the maximum numerical priority of sources to check". This means that all the sources with numerical priority higher than "max_priority" should not be checked, although in the implementation this parameter is ignored.
Steps to reproduce:
- 3 sources are attached to the context, with the priorities {-1, 0, 1}
- All the sources, added to the context return FALSE upon prepare*() and check*() calls
- Verify that return value of the g_main_context_check() is FALSE
- Verify that the only source, that was checked was the one with priority -1, [max_priority == -1]
g_main_context_check interface checks (actually calls the check*() function of the given source) all three sources, regardless of their numerical priority value.
Actual results:
Expected results:
Does this happen every time? Yes
Other information: The detailed bug description can be found at:
http://linuxtesting.org/results/report?num=D0004
Version: 2.14.x