linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: cki-project@redhat.com
Cc: yoyang@redhat.com, will@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: ❌ FAIL: Test report for for-kernelci (6.13.0-rc7, upstream-arm-next, 1950a0af)
Date: Sat, 18 Jan 2025 12:12:38 +0000	[thread overview]
Message-ID: <Z4uatgrJCdtiyUXH@arm.com> (raw)
In-Reply-To: <45567.125011714220601212@us-mta-568.us.mimecast.lan>

On Fri, Jan 17, 2025 at 07:22:04PM -0000, cki-project@redhat.com wrote:
> One or more kernel tests failed:
>     Unrecognized or new issues:
>         xfstests - btrfs
>              aarch64
>                    Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1629927092-aarch64-kernel_upt_56
>                    Non-passing ran subtests:
>                        ❌ FAIL btrfs:install_xfstests
>                        ❌ FAIL exit_code
>              aarch64
>                    Logs: https://datawarehouse.cki-project.org/kcidb/tests/redhat:1629927092-aarch64-kernel_upt_64
>                    Non-passing ran subtests:
>                        ❌ FAIL btrfs:install_xfstests
>                        ❌ FAIL exit_code

Looking at the logs, there seem to be some build error with xfstests,
unrelated to the kernel changes:

random_range.c:596:5: error: too many arguments to function 'srand48'; expected 0, have 1
  596 |     srand48(s);
      |     ^~~~~~~ ~

-- 
Catalin


      reply	other threads:[~2025-01-18 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17 19:22 ❌ FAIL: Test report for for-kernelci (6.13.0-rc7, upstream-arm-next, 1950a0af) cki-project
2025-01-18 12:12 ` Catalin Marinas [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=Z4uatgrJCdtiyUXH@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=cki-project@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=will@kernel.org \
    --cc=yoyang@redhat.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.
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 NNTP newsgroup(s).