From: kernel test robot <lkp@intel.com>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: linux-erofs@lists.ozlabs.org
Subject: [xiang-erofs:dev-test] BUILD SUCCESS 67039e1ee225d4b41dd8166791e130f237b68ce4
Date: Sat, 22 Feb 2025 19:05:24 +0800 [thread overview]
Message-ID: <202502221918.zpXPHTLw-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git dev-test
branch HEAD: 67039e1ee225d4b41dd8166791e130f237b68ce4 erofs: clean up header parsing for ztailpacking and fragments
elapsed time: 1450m
configs tested: 63
configs skipped: 1
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allyesconfig gcc-14.2.0
arc randconfig-001-20250221 gcc-13.2.0
arc randconfig-002-20250221 gcc-13.2.0
arm randconfig-001-20250221 gcc-14.2.0
arm randconfig-002-20250221 clang-19
arm randconfig-003-20250221 gcc-14.2.0
arm randconfig-004-20250221 clang-21
arm64 randconfig-001-20250221 clang-15
arm64 randconfig-002-20250221 clang-21
arm64 randconfig-003-20250221 clang-21
arm64 randconfig-004-20250221 gcc-14.2.0
csky randconfig-001-20250221 gcc-14.2.0
csky randconfig-002-20250221 gcc-14.2.0
hexagon allmodconfig clang-21
hexagon allyesconfig clang-18
hexagon randconfig-001-20250221 clang-21
hexagon randconfig-002-20250221 clang-21
i386 buildonly-randconfig-001-20250221 gcc-12
i386 buildonly-randconfig-002-20250221 gcc-12
i386 buildonly-randconfig-003-20250221 gcc-12
i386 buildonly-randconfig-004-20250221 gcc-12
i386 buildonly-randconfig-005-20250221 clang-19
i386 buildonly-randconfig-006-20250221 clang-19
loongarch randconfig-001-20250221 gcc-14.2.0
loongarch randconfig-002-20250221 gcc-14.2.0
nios2 randconfig-001-20250221 gcc-14.2.0
nios2 randconfig-002-20250221 gcc-14.2.0
parisc randconfig-001-20250221 gcc-14.2.0
parisc randconfig-002-20250221 gcc-14.2.0
powerpc randconfig-001-20250221 clang-21
powerpc randconfig-002-20250221 clang-21
powerpc randconfig-003-20250221 clang-17
powerpc64 randconfig-001-20250221 clang-21
powerpc64 randconfig-002-20250221 clang-21
powerpc64 randconfig-003-20250221 clang-19
riscv randconfig-001-20250221 clang-21
riscv randconfig-002-20250221 clang-21
s390 allmodconfig clang-19
s390 allyesconfig gcc-14.2.0
s390 randconfig-001-20250221 gcc-14.2.0
s390 randconfig-002-20250221 gcc-14.2.0
sh allmodconfig gcc-14.2.0
sh allyesconfig gcc-14.2.0
sh randconfig-001-20250221 gcc-14.2.0
sh randconfig-002-20250221 gcc-14.2.0
sparc allmodconfig gcc-14.2.0
sparc randconfig-001-20250221 gcc-14.2.0
sparc randconfig-002-20250221 gcc-14.2.0
sparc64 randconfig-001-20250221 gcc-14.2.0
sparc64 randconfig-002-20250221 gcc-14.2.0
um allmodconfig clang-21
um allyesconfig gcc-12
um randconfig-001-20250221 gcc-12
um randconfig-002-20250221 gcc-12
x86_64 allnoconfig clang-19
x86_64 buildonly-randconfig-001-20250221 gcc-12
x86_64 buildonly-randconfig-002-20250221 clang-19
x86_64 buildonly-randconfig-003-20250221 clang-19
x86_64 buildonly-randconfig-004-20250221 clang-19
x86_64 buildonly-randconfig-005-20250221 clang-19
x86_64 buildonly-randconfig-006-20250221 clang-19
xtensa randconfig-001-20250221 gcc-14.2.0
xtensa randconfig-002-20250221 gcc-14.2.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-22 11:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202502221918.zpXPHTLw-lkp@intel.com \
--to=lkp@intel.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.