From: Florin Sarbu <florin.sarbu@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Linux-yocto 3.0 crashes at do_patch...
Date: Tue, 22 May 2012 13:10:43 +0300 [thread overview]
Message-ID: <4FBB6623.10607@windriver.com> (raw)
In-Reply-To: <CAK18fxHfOZ0y07uuRfu6CVPR6KGbbH_NhEd8-HM-17sro3hAkw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 5364 bytes --]
Same for me again on a try today:
> | build/tmp-eglibc-eglibc/sysroots/x86_64-linux/usr/bin/scc: line 399:
> yocto/standard/beagleboard-standard: No such file or directory
> | ERROR. Could not find an excutable target for yocto/standard/base
> | ERROR. Could not locate meta series for yocto/standard/beagleboard
> | ERROR. Could not modify yocto/standard/base
> NOTE: package
> linux-yocto-3.0.24+git1+34e0d2b4b4e9778b31f9ea99ca43f0dc71a7ee23_1+6b4bf6173b0bd2d1619a8218bac66ebc4681dd35-r4:
> task do_patch: Failed
Florin
On 05/22/2012 01:02 PM, Andrei Gherzan wrote:
> Even after using your workaround i can still reproduce this issue.
> Yocto linux still fails.
>
> | ERROR. Could not find an excutable target for yocto/standard/base
> | ERROR. Could not locate meta series for yocto/standard/beagleboard
> | ERROR. Could not modify yocto/standard/base
> NOTE: package
> linux-yocto-3.0.24+git1+34e0d2b4b4e9778b31f9ea99ca43f0dc71a7ee23_1+6b4bf6173b0bd2d1619a8218bac66ebc4681dd35-r4:
> task do_patch: Failed
> ERROR: Task 3
> (/media/HDD/yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb
> <http://linux-yocto_3.0.bb>, do_patch) failed with exit code '1'
>
> On Thu, May 17, 2012 at 11:48 PM, Flanagan, Elizabeth
> <elizabeth.flanagan@intel.com <mailto:elizabeth.flanagan@intel.com>>
> wrote:
>
> On Thu, May 17, 2012 at 7:59 AM, Andrei Gherzan <andrei@gherzan.ro
> <mailto:andrei@gherzan.ro>> wrote:
> > Today i just gave another try.... same result.
>
> Responding here as well as the yocto list:
>
> A few people have been having this issue and after some discussion we
> think we have a root cause. Let me first explain what happened.
>
> The autobuilder infrastructure shares a common DL_DIR in order to
> optimize the builds and provide the source mirror. This DL_DIR is
> rsynced to the publicaly available source mirror on a regular basis.
> During our infrastructure upgrade the autobuilder attempted to pull
> the tar archive for linux-yocto-3.0
> (http://downloads.yoctoproject.org/mirror/sources/git2_git.yoctoproject.org.linux-yocto-3.0.tar.gz)
> but due to network issues related to our recent infrastructure upgrade
> the file ended up as a 0 byte file. This file was rsynced the the
> source mirror. A few days ago this was mentioned as an issue. Michael
> Halstead corrected the network issue and I manually removed the file.
> The autobuilder repulled the archive correctly and repopulated the
> source mirror with it.
>
> Things should have been ok at this point. However, we were still
> getting reports of people sporadically running into a 0 byte file. Not
> all the time, but some of the time. Michael Halstead and I just tailed
> out the apache logs with Tom Zanussi wgetting the problematic file,
> watching for failures. No failures were seen in the error logs however
> Tom was still getting sporadic 0 byte files. Which means that his
> request wasn't even hitting the server. I was not able to replicate
> this. The only difference we could see is that I generally do not go
> through a proxy whereas Tom was.
>
> Our theory at this point is that all of the people who are hitting
> this issue are going through a proxy and that their proxy setup has
> cached that 0 byte file and refuses to regenerate it. There isn't a
> lot we can do from our end about that other than suggest the following
> work around. If you run into odd fetch issues with *just* the
> linux-yocto-3.0 tar archive, clear out your DL_DIR of
> git2_git.yoctoproject.org.linux-yocto-3.0.tar.gz and set the
> following:
>
> PREMIRRORS ?= "\
> bzr://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
> cvs://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
> git://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
> hg://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
> osc://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
> p4://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
> svk://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
> svn://.*/.* http://autobuilder.yoctoproject.org/sources/ \n"
>
> MIRRORS =+ "\
> ftp://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
> http://.*/.* http://autobuilder.yoctoproject.org/sources/ \n \
> https://.*/.* http://autobuilder.yoctoproject.org/sources/ \n"
>
> This will force the fetch to go to the autobuilder host of sources and
> should work around any proxy caching issues. Then call your local IT
> folks and ask them to clear out your proxy cache. If you run into any
> fetch issues not related to this file, please let me know.
>
> -b
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> <mailto:Openembedded-core@lists.openembedded.org>
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[-- Attachment #2: Type: text/html, Size: 9792 bytes --]
next prev parent reply other threads:[~2012-05-22 10:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 10:09 Linux-yocto 3.0 crashes at do_patch Andrei Gherzan
2012-05-17 10:11 ` Florin Sarbu
2012-05-17 12:57 ` Bruce Ashfield
2012-05-17 13:38 ` Bruce Ashfield
2012-05-17 13:41 ` Andrei Gherzan
2012-05-17 14:56 ` Flanagan, Elizabeth
2012-05-17 14:59 ` Andrei Gherzan
2012-05-17 20:48 ` Flanagan, Elizabeth
2012-05-22 10:02 ` Andrei Gherzan
2012-05-22 10:10 ` Florin Sarbu [this message]
2012-05-22 13:20 ` Richard Purdie
2012-05-22 13:43 ` Andrei Gherzan
2012-05-22 15:53 ` Tom Zanussi
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=4FBB6623.10607@windriver.com \
--to=florin.sarbu@windriver.com \
--cc=openembedded-core@lists.openembedded.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