lp:jasmine-gjs : Git : Code : jasmine-gjs

Import details

Import Status: Reviewed

This repository is an import of the Git repository at https://github.com/ptomato/jasmine-gjs.git.

The next import is scheduled to run in 4 hours.

Last successful import was 1 hour ago.

Import started 1 hour ago on juju-98ee42-prod-launchpad-codeimport-4 and finished 1 hour ago taking 25 seconds — see the log

Import started 7 hours ago on juju-98ee42-prod-launchpad-codeimport-5 and finished 7 hours ago taking 20 seconds — see the log

Import started 13 hours ago on juju-98ee42-prod-launchpad-codeimport-4 and finished 13 hours ago taking 5 seconds — see the log

Import started 19 hours ago on juju-98ee42-prod-launchpad-codeimport-0 and finished 19 hours ago taking 15 seconds — see the log

Import started on 2024-04-18 on juju-98ee42-prod-launchpad-codeimport-1 and finished on 2024-04-18 taking 10 seconds — see the log

Import started on 2024-04-17 on juju-98ee42-prod-launchpad-codeimport-0 and finished on 2024-04-17 taking 10 seconds — see the log

Import started on 2024-04-17 on juju-98ee42-prod-launchpad-codeimport-5 and finished on 2024-04-17 taking 3 minutes — see the log

Import started on 2024-04-17 on juju-98ee42-prod-launchpad-codeimport-0 and finished on 2024-04-17 taking 20 seconds — see the log

Import started on 2024-04-17 on juju-98ee42-prod-launchpad-codeimport-5 and finished on 2024-04-17 taking 10 seconds — see the log

Name	Last Modified	Last Commit
master	2024-04-10 03:16:20 UTC 2024-04-10	bin: Fix exit code propagation Author: Martin Abente Lahaye Author Date: 2024-04-04 17:44:21 UTC bin: Fix exit code propagation Now that we're loading entrypoints as modules, exit codes no longer propagate in the same way. Therefore, we must do that explicitly through the system exit function. Without this the exit code is always ZERO and in practical terms all CI pipelines depending on this are always passing even when the tests are actually failing. See 7825a0c.
wip/loghandler	2015-03-02 06:47:46 UTC 2015-03-02	WIP for handling GJS log messages Author: Philip Chimento Author Date: 2015-03-02 06:47:46 UTC WIP for handling GJS log messages GJS exceptions can't be caught across the boundary of a signal handler. So if a signal handler or idle function throws an exception, then your test won't fail. Possibly Jasmine can even hang if no specs ever execute. However, this code won't work because g_set_log_handler() is not introspectable. [#4]