cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: "Pavel Machek" <pavel@ucw.cz>
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] arm64/renesas test failing for v4.19.148-cip35-rt15 (-rt64)
Date: Sat, 3 Oct 2020 23:49:39 +0200	[thread overview]
Message-ID: <20201003214939.GA3733@duo.ucw.cz> (raw)
In-Reply-To: <20201003151745.GA1399@duo.ucw.cz>


[-- Attachment #1.1: Type: text/plain, Size: 1467 bytes --]

Hi!

> I got test failure when I submitted -rt branch for testing.
> 
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/197703780
> 
> This seems to be "real" failure:

I re-ran the test with same sources, and failure is still there.

I tried rt+v4.19.147-cip35 -- e8bcfc1349886ef3cf6625a0bc9cd25ddf80112c
-- fails, too.

Let me try commit 1d9c4c7e291d5f49ab07402ef739f98fac6e7adb (tag:
v4.19.144-cip34). ... that one works.

To be sure, let's try older rt commit:
f15040b9d853b9cfbcdd4707d9be2593b42b000b ( v4.19.142-cip33-rt14 /
-rt63). That one works ok.

-rt63-rebase and -rt64-rebase trees have same commits on top.. in
fact, they seem to have same commits. That probably means nothing
changed in -rt. But it looks like there's commit in -stable, touching
relevant area.

commit fb3a780e7a76cf8efb055f8322ec039923cee41f
Author: Yuusuke Ashizuka <ashiduka@fujitsu.com>
Date:   Thu Aug 20 18:43:07 2020 +0900

    ravb: Fixed to be able to unload modules

Let me investigate some more.

> With no network, it is easy to understand that tests would fail.
> 
> x86_siemens, OTOH, seems to be infrastructure error
> (bootloader-interrupt timed out after 599 seconds).

This one went away when I resubmitted same kernel... so lets ignore it.

Best regards,
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5493): https://lists.cip-project.org/g/cip-dev/message/5493
Mute This Topic: https://lists.cip-project.org/mt/77282618/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


  reply	other threads:[~2020-10-03 21:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-03 15:17 [cip-dev] arm64/renesas test failing for v4.19.148-cip35-rt15 (-rt64) Pavel Machek
2020-10-03 21:49 ` Pavel Machek [this message]
2020-10-04  7:31   ` [cip-dev] Pending problem in v4.19.148 -- " Pavel Machek

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=20201003214939.GA3733@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=cip-dev@lists.cip-project.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 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).