emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: emacs-orgmode@gnu.org
Subject: [ANN] We are now regularily testing Org main branch against Emacs 26, 27, 28
Date: Sun, 16 Oct 2022 08:03:04 +0200	[thread overview]
Message-ID: <87tu44uwyv.fsf@bzg.fr> (raw)

Hi all,

thanks to joint efforts by Christian Köstlin and Ihor, we are running
the Org test suite from the Org main branch against Emacs 26, 27, 28.

Every three hours, a script from the orgmode.org server checks if the
Org main branch changed.

If yes, we run the Org test suite against Emacs 26, 27 and 28.

If a test fails, a failure report is sent to a new mailing list:
https://lists.sr.ht/~bzg/org-build-failures and we can inspect what
did go wrong.

If a test fails again (i.e. there was a failure, then the repo was
updated, then there is a failure again for the same test), reports are
sent to Ihor, Christian and me, not to the dedicated list.

Tests are performed by running builds on sr.ht.  You can read the
builds in this new repository: https://git.sr.ht/~bzg/org-mode-tests

We are now testing this setup: if it useful enough, we will redirect
failure reports to the Org mailing list, while using the new one for
repeated failures, so as to not spam the list.

In the future, resources at https://git.sr.ht/~bzg/org-mode-tests
will also perhaps help contributors defining new ways on how to run
tests, beyond the current way ("make test").

Patch submitters are required to run the tests themselves before
submitting a patch: we don't rely on this new setup to test patches,
only to catch errors that may inadvertently slip through the cracks.

Thanks again to Christian and Ihor for setting this up!

-- 
 Bastien


             reply	other threads:[~2022-10-16  6:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16  6:03 Bastien [this message]
2022-10-17 14:54 ` [ANN] We are now regularily testing Org main branch against Emacs 26, 27, 28 Kaushal Modi

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=87tu44uwyv.fsf@bzg.fr \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    /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).