From: Gao Xiang <xiang@kernel.org>
To: Yifan Zhao <zhaoyifan@sjtu.edu.cn>
Cc: linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH] erofs-utils: introduce GitHub Actions CI
Date: Sun, 21 Jan 2024 11:33:49 +0800 [thread overview]
Message-ID: <ZayQnZ9dI3CUhnSe@debian> (raw)
In-Reply-To: <20240120152557.178210-1-zhaoyifan@sjtu.edu.cn>
Hi Yifan,
On Sat, Jan 20, 2024 at 11:25:57PM +0800, Yifan Zhao wrote:
> This commit introduces a new CI workflow configuration designed to
> automate the testing process for erofs-utils. This CI is based on the
> free GitHub Actions for we have a fork in GitHub. The CI will be
> triggered on every push to the {main,dev,experimental} branch.
>
> Currently, we have only a simple test for ensuring the correctness of
> mkfs.erofs, which covers a small subset of its extended options
> including dedupe, fragments, ztailpacking and {lz4,lz4hc,deflate}
> compression algorithms. It creates a EROFS image using Linux v6.7 source
> code as the workload, then extracts it using fsck.erofs and compares the
> sha256sum of the extracted files with the original ones.
Personally, I tend to avoid relying on any Github infrastructure for
the erofs-utils codebase. Previously it already checked enwik8
correctness in the Github CI, see:
https://github.com/erofs/erofsnightly/blob/main/.github/workflows/smoking.yml#L185
If you would like to add a Github CI for Linux codebase, please
update
https://github.com/erofs/erofsnightly/actions
nightly CI instead.
Thanks,
Gao Xiang
>
> Signed-off-by: Yifan Zhao <zhaoyifan@sjtu.edu.cn>
prev parent reply other threads:[~2024-01-21 3:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 15:25 [PATCH] erofs-utils: introduce GitHub Actions CI Yifan Zhao
2024-01-21 3:33 ` Gao Xiang [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZayQnZ9dI3CUhnSe@debian \
--to=xiang@kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=zhaoyifan@sjtu.edu.cn \
/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.
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).