From: Michael Albinus <michael.albinus@gmx.de>
To: Peter Oliver <p.d.oliver@mavit.org.uk>
Cc: Yuan Fu <casouri@gmail.com>, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Validating tree-sitter major modes and grammar
Date: Sat, 28 Dec 2024 13:02:38 +0100 [thread overview]
Message-ID: <87v7v4582p.fsf@gmx.de> (raw)
In-Reply-To: <87msgi72r8.fsf@gmx.de> (Michael Albinus's message of "Thu, 26 Dec 2024 18:50:03 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
Hi Peter & Yuan,
>>> Is it possible for EMBA to run a CI which produces a HTML webpage, and host that webpage somewhere? I’m referring to this idea of Peter’s.
>>
>> In general it is possible, using a GitLab feature called Pages (https://emba.gnu.org/help/user/project/pages/index.md).
>>
>> Some configuration is required
>> (https://emba.gnu.org/help/administration/pages/index.md). I don’t
>> know if this has been done for EMBA (but I suspect not, because
>> https://emba.gnu.org/emacs/emacs/pages returns 404; alternatively,
>> it’s possible the feature simply needs switching on at
>> https://emba.gnu.org/emacs/emacs/edit#js-general-project-settings).
>>
>> Once this is done, you don’t have to do much more than, from your CI job, write HTML files to a directory called pages.
>>
>>> I’m thinking of a table where rows are languages, columns are Emacs releases (29, 30, master), and cells are the latest revision of a language grammar that’s compatible with an Emacs release.
>>
>> Sounds perfect.
>
> Nice. I'll see whether I can do something useful with this.
As a starting point, we could use the JUnit reports, which are already
generated. They are not formatted to what we want, but they contain all
test results in XML files for better access.
See for example
<https://emba.gnu.org/emacs/emacs/-/pipelines/31215/test_report> and
click on "Tests". Choose job test-tree-sitter.
There are no data when you inspect "View details", but this can be changed.
Best regards, Michael.
next prev parent reply other threads:[~2024-12-28 12:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 9:09 Validating tree-sitter major modes and grammar Yuan Fu
2024-12-20 12:24 ` Eli Zaretskii
2024-12-20 16:22 ` Yuan Fu
2024-12-23 0:44 ` Björn Bidar
[not found] ` <868qs6vd76.fsf@aarsen.me>
2024-12-24 1:16 ` Yuan Fu
2024-12-24 3:12 ` Yuan Fu
2024-12-24 12:19 ` Eli Zaretskii
2024-12-24 21:30 ` Yuan Fu
2024-12-24 23:09 ` Dmitry Gutov
2024-12-25 8:39 ` Yuan Fu
2024-12-26 2:23 ` Dmitry Gutov
[not found] ` <6768b29d.050a0220.1b40f2.5574SMTPIN_ADDED_BROKEN@mx.google.com>
2024-12-24 3:20 ` Yuan Fu
2024-12-24 12:36 ` Peter Oliver
2024-12-24 14:20 ` Michael Albinus
2024-12-24 22:20 ` Yuan Fu
2024-12-25 8:20 ` Michael Albinus
2024-12-25 9:33 ` Yuan Fu
2024-12-25 13:51 ` Michael Albinus
2024-12-26 12:54 ` Peter Oliver
2024-12-26 17:50 ` Michael Albinus
2024-12-28 12:02 ` Michael Albinus [this message]
2024-12-30 8:08 ` Yuan Fu
2024-12-24 22:14 ` Yuan Fu
2024-12-24 21:36 ` Björn Bidar
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v7v4582p.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=p.d.oliver@mavit.org.uk \
/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.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).