summaryrefslogtreecommitdiff
path: root/src/tests/ecore/efl_app_test_promise.c (follow)
AgeCommit message (Collapse)Author
2019-09-12efl_app_test_promise: fix warning (no returned value)Vincent Torri
Test Plan: compilation Reviewers: cedric, zmike, raster Reviewed By: zmike Subscribers: #reviewers, #committers Tags: #efl Differential Revision: https://phab.enlightenment.org/D9926
2019-06-20ecore: do not rely on implicit rules for memory lifecycle during test.Cedric BAIL
Summary: alloca force the memory to be accessible for the entire duration of the scope of the function it is called from. This will garantee that the memory pointer are not recycled under our feet before we check them. T8020 Reviewers: zmike Reviewed By: zmike Subscribers: #reviewers, #committers Tags: #efl Maniphest Tasks: T8020 Differential Revision: https://phab.enlightenment.org/D9127
2019-05-09ecore: make sure that ecore stay initialized during the full test.Cedric BAIL
efl_app_test_promise.c is slightly special and corrective action have to be taken to make sure that ecore_init return the right value when the no fork mode of libcheck is used. Reviewed-by: Mike Blumenkrantz <michael.blumenkrantz@gmail.com> Reviewed-by: Marcel Hollerbach <mail@marcel-hollerbach.de> Differential Revision: https://phab.enlightenment.org/D8566
2019-04-02tests: unset eina log callback at end of each efl_app promise testMike Blumenkrantz
Summary: ensure that this doesn't trigger cascading errors Reviewers: cedric Reviewed By: cedric Subscribers: cedric, #reviewers, #committers Tags: #efl Differential Revision: https://phab.enlightenment.org/D8514
2019-03-08efl.loop_timer: rename all methods/properties/eventsMike Blumenkrantz
Summary: avoid potential future conflict by not using conflict-able names ref T7731 Reviewers: segfaultxavi Reviewed By: segfaultxavi Subscribers: cedric, #reviewers, #committers Tags: #efl_api Maniphest Tasks: T7731 Differential Revision: https://phab.enlightenment.org/D8256
2019-01-09efl: remove warning due to unused variable/parameters.Cedric BAIL
Reviewers: #committers, felipealmeida, zmike Reviewed By: #committers, felipealmeida, zmike Subscribers: zmike, YOhoho, Hermet, #reviewers, #committers Tags: #efl Differential Revision: https://phab.enlightenment.org/D7554
2018-12-07ecore: add a full test for efl_future_then and efl_future_chain.Cedric BAIL
Summary: Depends on D7392 Reviewers: bu5hm4n, segfaultxavi Reviewed By: bu5hm4n, segfaultxavi Subscribers: #reviewers, #committers Tags: #efl Maniphest Tasks: T7472 Differential Revision: https://phab.enlightenment.org/D7393
2018-12-07ecore: fix typo in comments.Cedric BAIL
Summary: Depends on D7391 Reviewers: bu5hm4n, segfaultxavi, kimcinoo Reviewed By: kimcinoo Subscribers: kimcinoo, #reviewers, #committers Tags: #efl Maniphest Tasks: T7472 Differential Revision: https://phab.enlightenment.org/D7392
2018-12-07ecore: efl_app_suite doesn't need to depends on Efl_Net.Cedric BAIL
Summary: Depends on D7381 Reviewers: bu5hm4n, segfaultxavi Reviewed By: segfaultxavi Subscribers: #reviewers, #committers Tags: #efl Maniphest Tasks: T7472 Differential Revision: https://phab.enlightenment.org/D7390
2018-12-07eo: make efl_future_then have a data pointer in addition of the object pointer.Cedric BAIL
Summary: In the case when you have multiple future in flight related to one object, you couldn't use the previous version of efl_future_then. Now all function calls take a void* pointer that allow multiple future to have their private data request data accessible in all the callback. This should not break released API as Eo.h is not released yet and so was efl_future_Eina_FutureXXX_then. Depends on D7332 Reviewers: felipealmeida, segfaultxavi, vitor.sousa, SanghyeonLee, bu5hm4n Reviewed By: segfaultxavi Subscribers: #reviewers, #committers Tags: #efl Maniphest Tasks: T7472 Differential Revision: https://phab.enlightenment.org/D7379
2018-05-24Revert "efl_add_ref - fis to use efl_add properly with a parent."Cedric BAIL
This reverts commit 2fb5cc3ad09f6aaf82b5d1131ac5ed22ed848bd4. Most of this change where wrong as they didn't affect the destruction of the object. efl_add_ref allow for manual handling of the lifecycle of the object and make sure it is still alive during destructor. efl_add will not allow you to access an object after invalidate also efl.parent.get will always return NULL once the object is invalidated. Differential Revision: https://phab.enlightenment.org/D6062
2018-04-10tests: split efl_app promise tests into separate test casesMike Blumenkrantz
Summary: each test case can run in parallel, so this provides a ~300% speedup ref T6850 Depends on D5904 Reviewers: stefan_schmidt Subscribers: cedric Maniphest Tasks: T6850 Differential Revision: https://phab.enlightenment.org/D5905
2018-04-10tests: move ecore promise tests into efl_app_suiteMike Blumenkrantz
Summary: ref T6815 Depends on D5902 Reviewers: stefan_schmidt Subscribers: cedric Maniphest Tasks: T6815 Differential Revision: https://phab.enlightenment.org/D5903