On Sun, 7 Jan 2024 14:01:31 -0800 Ross Vandegrift <r...@kallisti.us> said:
[0/1] Running all tests. 1/39 eo-mixins OK 0.45s 2/39 eo-mixins-dbg OK 0.43s 3/39 eo-interface OK 0.42s 4/39 eo-interface-dbg OK 0.40s 5/39 eo-function-overrides OK 0.39s 6/39 eo-function-overrides-dbg OK 0.37s 7/39 eo-composite-objects OK 0.34s 8/39 eo-composite-objects-dbg OK 0.32s 9/39 eo-children OK 0.32s 10/39 eo-children-dbg OK 0.31s 11/39 eo-access OK 0.29s 12/39 eo-access-dbg OK 0.27s 13/39 emile-suite OK 0.26s 14/39 eet-suite OK 0.25s 15/39 ector-suite OK 0.10s 16/39 eina OK 0.68s 17/39 eo-signals OK 0.62s 18/39 eo-signals-dbg OK 0.61s 19/39 eo-constructors OK 0.50s 20/39 eo-constructors-dbg OK 0.49s 21/39 eo-suite-dbg OK 0.68s 22/39 eo-suite-fallback OK 0.70s 23/39 eo-suite OK 0.76s 24/39 efl-suite OK 0.49s 25/39 efreet-suite OK 0.21s 26/39 elput-suite OK 0.30s 27/39 edje-suite OK 0.37s 28/39 eldbus-suite OK 0.74s 29/39 eolian OK 1.09s 30/39 efl-app OK 0.91s 31/39 ecore_wl2-suite OK 0.88s 32/39 ecore_con-suite OK 0.93s 33/39 eio-suite OK 2.02s 34/39 ecore-suite OK 2.36s 35/39 eeze-suite OK 6.63s 36/39 efl_ui_spec-suite OK 7.15s 37/39 elementary-suite OK 13.98s 38/39 evas-suite OK 14.10s 39 does fail just one thing... a pretty "doesnt affect anything" test for focus for efl ui api. i disabled that test now so it all passes for me - no timeouts. i'm going to guess something is missing in the env? missing hmm dbus daemon? something else? some env missing like xdg runtime dir ... or something? but eina test suite should not need all of that sho it shouldnt be timing out - if you just run e.g. the eina suite e.g. ./src/tests/eina/eina_suite what happens? it should complete in almost no time (like a fraction of a second)... > Hello, > > It's been a while since I used the EFL test suite, not sure if I'm forgetting > something or if I've found a problem. > > On 1.27.0, `ninja test` runs into a bunch of timeouts: > > Summary of Failures: > > 20/38 eina TIMEOUT 30.11s > 21/38 eo-suite TIMEOUT 30.10s > 22/38 eo-suite-dbg TIMEOUT 30.10s > 23/38 eo-suite-fallback TIMEOUT 30.09s > 24/38 efl-suite TIMEOUT 30.04s > 25/38 emile-suite TIMEOUT 30.04s > 26/38 eet-suite TIMEOUT 30.03s > 27/38 eldbus-suite TIMEOUT 30.03s > 28/38 ecore-suite TIMEOUT 30.02s > 29/38 efl-app TIMEOUT 30.02s > 30/38 ecore_con-suite TIMEOUT 30.07s > 31/38 eeze-suite TIMEOUT 30.06s > 32/38 efreet-suite TIMEOUT 30.01s > 33/38 edje-suite TIMEOUT 30.01s > 34/38 elementary-suite TIMEOUT 30.02s > 35/38 efl-ui-suite TIMEOUT 30.02s (exit status 255 or > signal 127 SIGinvalid) 36/38 evas-suite TIMEOUT 60.01s > 38/38 efl_ui_spec-suite TIMEOUT 60.01s > > But at least some of the individual test suites succeed: > > $ EFL_RUN_IN_TREE=1 ./build/src/tests/evas/evas_suite &> out > $ grep Failures out > 100%: Checks: 1, Failures: 0, Errors: 0 > 100%: Checks: 1, Failures: 0, Errors: 0 > 100%: Checks: 1, Failures: 0, Errors: 0 > 100%: Checks: 1, Failures: 0, Errors: 0 > 100%: Checks: 3, Failures: 0, Errors: 0 > 100%: Checks: 2, Failures: 0, Errors: 0 > 100%: Checks: 3, Failures: 0, Errors: 0 > 100%: Checks: 2, Failures: 0, Errors: 0 > 100%: Checks: 3, Failures: 0, Errors: 0 > 100%: Checks: 3, Failures: 0, Errors: 0 > 100%: Checks: 7, Failures: 0, Errors: 0 > 100%: Checks: 10, Failures: 0, Errors: 0 > 100%: Checks: 16, Failures: 0, Errors: 0 > 100%: Checks: 4, Failures: 0, Errors: 0 > 100%: Checks: 37, Failures: 0, Errors: 0 > 100%: Checks: 2, Failures: 0, Errors: 0 > 100%: Checks: 25, Failures: 0, Errors: 0 > > > I'm redirecting to a file instead of a pipe - if I use a pipe, the test suite > hangs forever at the end. Seems like this could be related? > > $ EFL_RUN_IN_TREE=1 ./build/src/tests/evas/evas_suite 2>&1 | grep Failures > 100%: Checks: 1, Failures: 0, Errors: 0 > 100%: Checks: 1, Failures: 0, Errors: 0 > 100%: Checks: 1, Failures: 0, Errors: 0 > 100%: Checks: 3, Failures: 0, Errors: 0 > 100%: Checks: 3, Failures: 0, Errors: 0 > 100%: Checks: 1, Failures: 0, Errors: 0 > 100%: Checks: 2, Failures: 0, Errors: 0 > 100%: Checks: 2, Failures: 0, Errors: 0 > 100%: Checks: 3, Failures: 0, Errors: 0 > 100%: Checks: 3, Failures: 0, Errors: 0 > 100%: Checks: 7, Failures: 0, Errors: 0 > 100%: Checks: 10, Failures: 0, Errors: 0 > 100%: Checks: 4, Failures: 0, Errors: 0 > 100%: Checks: 16, Failures: 0, Errors: 0 > 100%: Checks: 37, Failures: 0, Errors: 0 > 100%: Checks: 2, Failures: 0, Errors: 0 > 100%: Checks: 25, Failures: 0, Errors: 0 <- never returns, but looks done > > Thanks for any pointers, > Ross > > > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
