From: Pavel Machek <pavel@denx.de>
To: Pavel Machek <pavel@denx.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
"Bhola, Bikram" <Bikram_Bhola@mentor.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] I need de0-nano testing for -rt release was Re: 4.19.106-cip21-rt8 problems on de0-nano
Date: Mon, 16 Mar 2020 12:59:14 +0100 [thread overview]
Message-ID: <20200316115913.GA18883@duo.ucw.cz> (raw)
In-Reply-To: <20200315094201.GA23740@duo.ucw.cz>
[-- Attachment #1.1: Type: text/plain, Size: 1239 bytes --]
Hi!
> > Both de0-nano and IPC227E targets are up and running. I have monitored for test jobs on it and those completed successfully.
> >
> > Thank You!!
>
> There's still something broken with the testing. renesas_shmobile
> initially failed (okay after restart), rest failed:
>
> https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/126355890
https://lava.ciplatform.org/scheduler/job/12718
Going through the logs:
progress 90% (81MB)
progress 95% (86MB)
progress 100% (90MB)
90MB downloaded in 383.03s (0.24MB/s)
end: 1.3.1 http-download (duration 00:06:23) [common]
case: http-download
case_id: 403737
definition: lava
duration: 383.03
extra: ...
level: 1.3.1
namespace: common
result: pass
tftp-deploy timed out after 1283 seconds
end: 1.3 download-retry (duration 00:06:24) [common
You are not trying to do tftp over WAN, are you?
Seeing the download speeds... would it make sense to do downloads with
rsync? Root filesystems (etc) are not changing too often, so that
should provide some speedups.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev
next prev parent reply other threads:[~2020-03-16 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 9:15 [cip-dev] 4.19.106-cip21-rt8 problems on de0-nano Pavel Machek
2020-03-03 9:23 ` Pavel Machek
2020-03-03 17:10 ` Pavel Machek
2020-03-03 21:28 ` Pavel Machek
2020-03-04 19:53 ` Jan Kiszka
2020-03-09 10:21 ` [cip-dev] I need de0-nano testing for -rt release was " Pavel Machek
2020-03-09 18:52 ` Jan Kiszka
2020-03-10 16:50 ` Bhola, Bikram
[not found] ` <78fd4f1df8034021ae195b8287cf2f29@SVR-IES-MBX-03.mgc.mentorg.com>
2020-03-11 15:36 ` Bhola, Bikram
2020-03-15 9:42 ` [cip-dev] " Pavel Machek
2020-03-16 11:59 ` Pavel Machek [this message]
2020-03-16 16:05 ` Bhola, Bikram
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=20200316115913.GA18883@duo.ucw.cz \
--to=pavel@denx.de \
--cc=Bikram_Bhola@mentor.com \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.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