From: vijai kumar <vijaikumar.kanagarajan@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 1/2] rootfs: Make rootfs finalize a separate task
Date: Tue, 7 Apr 2020 12:23:43 +0530 [thread overview]
Message-ID: <CALLGG_+EYRyK1iTaSEy1EOcgNqq_-PMP0spJ7Z9ssh_ZCGpXbA@mail.gmail.com> (raw)
In-Reply-To: <b88170d7-c0b0-7093-008e-59af5cc8446a@siemens.com>
On Tue, Apr 7, 2020 at 12:15 PM Jan Kiszka <jan.kiszka@siemens.com> wrote:
>
> On 07.04.20 08:19, vijai kumar wrote:
> >
> >
> > On Friday, April 3, 2020 at 2:20:34 PM UTC+5:30, vijai kumar wrote:
> >
> > On Fri, Apr 3, 2020 at 2:00 PM Baurzhan Ismagulov <ibr@radix50.net
> > <mailto:ibr@radix50.net>> wrote:
> > >
> > > On Fri, Apr 03, 2020 at 12:20:41PM +0530, vijai kumar wrote:
> > > > > > A fetch should not be affected by what is in next. I would
> > guess/hope
> > > > > > that you just into a temporary network hickup.
> > > > >
> > > > > I am assuming the same. I hit it in a couple of builds.
> > Anyway my
> > > > > local build got through. Triggered another job in CI to see
> > if this
> > > > > issues goes away.
> > > >
> > > > I am getting this fetcher issue consistently (packages differ)
> > in the
> > > > ISAR CI build. All my local builds went through. I believe
> > there is
> > > > more to it. Some proxy issues affecting apt fetch in CI?
> > >
> > > We had various network issues before, but I haven't seen such one
> > till now.
> > > At least Isar (next) fast built fine till now. Seems that
> > applying your patch
> > > uncovers some issue...
> >
> > Yes. the apt-get source download call in my patch is what fails with
> > the below error.
> >
> > "Writing more data than expected (<size> > <size>)"
> >
> > A quick google for similar issues got me to the below link which
> > recommends to use a set of apt options. I tried but without success.
> >
> > https://github.com/jenkinsci/docker/issues/543
> > <https://github.com/jenkinsci/docker/issues/543>
> >
> > Thanks,
> > Vijai Kumar K
> >
> >
> > Hi Baurzhan,
> >
> > The problem still exists in CI[1]. I am trying to root cause it. I am
> > not sure how much I can proceed, since its mostly a black box for me.
> >
> > E
> > : Failed to fetch http://deb.debian.org/debian/pool/main/l/linux/linux_4.9.210.orig.tar.xz Writing more data than expected (94933088 > 94867552)
> >
> >
> > [1]http://ci.isar-build.org:8080/job/isar_vkk_devel/49/consoleText
> >
>
> I'll stick this into our CI as well to see if it reproduces there.
>
Thanks.
> Is the error on different packages or always on this one?
It is on different packages. I have seen glibc and some other packages fail.
Best,
Vijai Kumar K
>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-04-07 6:53 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 14:06 [PATCH] rootfs: Make rootfs_postprocess_finalize the last step Vijai Kumar K
2020-02-06 17:21 ` Jan Kiszka
2020-02-06 17:47 ` vijai kumar
2020-02-06 18:09 ` Jan Kiszka
2020-02-06 18:28 ` vijai kumar
2020-02-10 5:37 ` [PATCH v2] rootfs: Make rootfs finalize a separate task Vijai Kumar K
2020-02-11 11:38 ` Henning Schild
2020-02-11 14:14 ` vijai kumar
2020-02-11 15:20 ` Henning Schild
2020-02-11 18:07 ` Jan Kiszka
2020-02-13 10:08 ` [PATCH v2 1/2] " Vijai Kumar K
2020-02-13 10:08 ` [PATCH v2 2/2] meta: cache deb srcs as part of postprocessing Vijai Kumar K
2020-02-14 5:48 ` [PATCH v3 1/2] rootfs: Make rootfs finalize a separate task Vijai Kumar K
2020-02-14 5:48 ` [PATCH v3 2/2] meta: cache deb srcs as part of postprocessing Vijai Kumar K
2020-02-14 8:19 ` Jan Kiszka
2020-02-14 8:41 ` vijai kumar
2020-02-14 8:45 ` vijai kumar
2020-03-11 7:16 ` [PATCH v3 1/2] rootfs: Make rootfs finalize a separate task vijai kumar
2020-04-01 7:25 ` vijai kumar
2020-04-01 8:19 ` Henning Schild
2020-04-01 10:29 ` vijai kumar
2020-04-03 6:50 ` vijai kumar
2020-04-03 8:30 ` Baurzhan Ismagulov
2020-04-03 8:50 ` vijai kumar
2020-04-03 13:05 ` [PATCH v4 " Vijai Kumar K
2020-04-03 13:05 ` [PATCH v4 2/2] meta: cache deb srcs as part of postprocessing Vijai Kumar K
2020-04-07 6:44 ` Jan Kiszka
2020-04-07 6:58 ` vijai kumar
2020-04-07 7:04 ` Jan Kiszka
2020-04-07 7:59 ` vijai kumar
2020-04-07 8:38 ` Jan Kiszka
2020-04-07 9:08 ` vijai kumar
2020-04-07 9:40 ` vijai kumar
2020-04-08 8:13 ` Baurzhan Ismagulov
2020-04-08 10:04 ` vijai kumar
2020-04-08 13:32 ` vijai kumar
2020-04-15 6:44 ` vijai kumar
2020-04-15 7:28 ` Jan Kiszka
2020-04-15 13:20 ` vijai kumar
2020-04-15 13:44 ` Jan Kiszka
2020-04-08 10:04 ` Henning Schild
2020-04-08 10:37 ` vijai kumar
2020-04-08 12:30 ` Henning Schild
2020-04-15 12:29 ` vijai kumar
2020-04-15 18:19 ` Henning Schild
2020-04-16 15:57 ` vijai kumar
2020-04-16 17:29 ` Henning Schild
2020-04-07 6:19 ` [PATCH v3 1/2] rootfs: Make rootfs finalize a separate task vijai kumar
2020-04-07 6:45 ` Jan Kiszka
2020-04-07 6:53 ` vijai kumar [this message]
2020-04-07 7:12 ` Baurzhan Ismagulov
2020-04-07 8:04 ` vijai kumar
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=CALLGG_+EYRyK1iTaSEy1EOcgNqq_-PMP0spJ7Z9ssh_ZCGpXbA@mail.gmail.com \
--to=vijaikumar.kanagarajan@gmail.com \
--cc=isar-users@googlegroups.com \
--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