From: Ihor Radchenko <yantar92@posteo.net>
To: Bastien Guerry <bzg@gnu.org>
Cc: Yasushi SHOJI <yasushi.shoji@gmail.com>,
emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: [BUG] CI jobs do not appear to be running
Date: Thu, 19 Oct 2023 07:49:49 +0000 [thread overview]
Message-ID: <87sf67dpb6.fsf@localhost> (raw)
In-Reply-To: <87jzrkttnt.fsf@bzg.fr>
Bastien Guerry <bzg@gnu.org> writes:
>> https://lists.sr.ht/~bzg/org-build-failures ran the tests right after
>> <https://git.sr.ht/~bzg/org-mode-tests/commit/6a6d21723d7b60020a711382cdb40a3c3bbd9112>,
>> but my recent Org commits did not trigger anything.
>
> Perhaps your email was sent less than three hours after the last
> checks (I didn't check).
>
> Can you check again after the next commits? The cron job on the
> machine is configured correctly and should run. I'll see what's
> wrong if it does not run.
Still nothing, even though I did not address some recent
failures, like "FAILED ob-octave/session-multiline".
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-10-19 7:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 1:13 Current Org-mode does not work with Emacs 27 Yasushi SHOJI
2023-10-16 7:52 ` [BUG] CI jobs do not appear to be running (was: Current Org-mode does not work with Emacs 27) Ihor Radchenko
2023-10-16 10:03 ` [BUG] CI jobs do not appear to be running Bastien Guerry
2023-10-17 8:26 ` Ihor Radchenko
2023-10-18 4:56 ` Bastien Guerry
2023-10-19 7:49 ` Ihor Radchenko [this message]
2023-10-19 13:18 ` Bastien Guerry
2023-10-24 8:48 ` Ihor Radchenko
2023-10-24 12:19 ` Bastien Guerry
2023-10-28 14:46 ` Bastien Guerry
2023-10-16 8:25 ` Current Org-mode does not work with Emacs 27 Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sf67dpb6.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=yasushi.shoji@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).