ecore: fix that timers are not called in the order they were registered.
authorHosang Kim <hosang12.kim@samsung.com>
Thu, 2 Aug 2018 13:14:15 +0000 (09:14 -0400)
committerYeongjong Lee <yj34.lee@samsung.com>
Wed, 8 Aug 2018 01:54:15 +0000 (10:54 +0900)
commit0a1688312d28a42563e844fd4b4f34f0f2276140
treea086233920cbb89808fb8103494b45afcca197aa
parent7326b3a9c8b9dc7a54a101a82dc7908600cd0249
ecore: fix that timers are not called in the order they were registered.

Summary:
Timers are not called in the order they were registered.
Because when current timer is deleted, getting next timer is called twice.

Test Plan:
<error>
Timer1 expired after 0.001 seconds.
Timer3 expired after 0.001 seconds.
Timer5 expired after 0.001 seconds.
Timer7 expired after 0.001 seconds.
Timer2 expired after 0.001 seconds.
Timer6 expired after 0.001 seconds.
Timer4 expired after 0.001 seconds.
Timer8 expired after 0.001 seconds.
<correct>
Timer1 expired after 0.001 seconds.
Timer2 expired after 0.001 seconds.
Timer3 expired after 0.001 seconds.
Timer4 expired after 0.001 seconds.
Timer5 expired after 0.001 seconds.
Timer6 expired after 0.001 seconds.
Timer7 expired after 0.001 seconds.
Timer8 expired after 0.001 seconds.|

{F3268233}

Reviewers: Hermet, Jaehyun_Cho, zmike, SanghyeonLee

Reviewed By: zmike

Subscribers: cedric, #committers, zmike

Tags: #efl_tests

Differential Revision: https://phab.enlightenment.org/D6700
src/lib/ecore/ecore_timer.c
src/tests/ecore/ecore_test_timer.c