From: Bastien Guerry <bzg@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
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: Wed, 18 Oct 2023 06:56:54 +0200 [thread overview]
Message-ID: <87jzrkttnt.fsf@bzg.fr> (raw)
In-Reply-To: <87v8b5fyd5.fsf@localhost> (Ihor Radchenko's message of "Tue, 17 Oct 2023 08:26:46 +0000")
Hi Ihor,
Ihor Radchenko <yantar92@posteo.net> writes:
> May you also check if new commits in Org repo still trigger the check?
New commits in Org repo don't trigger the checks directly.
Instead, there is a cron job running every three hours and running the
checks iff there are new commits.
> 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.
Thanks!
--
Bastien
next prev parent reply other threads:[~2023-10-18 4:57 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 [this message]
2023-10-19 7:49 ` Ihor Radchenko
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=87jzrkttnt.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
--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).