From: Steve Sakoman <steve@sakoman.com>
To: yocto@lists.yoctoproject.org
Subject: [yocto-autobuilder-helper][dunfell 0/3] Patch review
Date: Tue, 22 Feb 2022 05:20:11 -1000 [thread overview]
Message-ID: <cover.1645543004.git.steve@sakoman.com> (raw)
I'm seeing intermittent timeout errors when starting an a-full build:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/3267
This set of patches from master seems to fix the issue.
The following changes since commit fe26983bb39a6a51eea3c0fe87dbc6a016abd85d:
config.json: Add other repo defaults to fix check-layer-nightly for meta-aws (2022-01-07 15:32:16 +0000)
are available in the Git repository at:
git://git.yoctoproject.org/yocto-autobuilder-helper contrib/sakoman
http://git.yoctoproject.org/cgit.cgi/yocto-autobuilder-helper/log/?h=contrib/sakoman
Richard Purdie (3):
scripts/prepare-shared-repos: Use tmpfs for speed
prepare-shared-repos: Make it clear when rsync starts in logs
shared-repos: Use tar instead of rsync for speed
scripts/prepare-shared-repos | 5 +++--
scripts/send-qa-email | 6 ++++--
scripts/shared-repo-unpack | 9 ++++++---
3 files changed, 13 insertions(+), 7 deletions(-)
--
2.25.1
next reply other threads:[~2022-02-22 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 15:20 Steve Sakoman [this message]
2022-02-22 15:20 ` [yocto-autobuilder-helper][dunfell 1/3] scripts/prepare-shared-repos: Use tmpfs for speed Steve Sakoman
2022-02-22 15:20 ` [yocto-autobuilder-helper][dunfell 2/3] prepare-shared-repos: Make it clear when rsync starts in logs Steve Sakoman
2022-02-22 15:20 ` [yocto-autobuilder-helper][dunfell 3/3] shared-repos: Use tar instead of rsync for speed Steve Sakoman
-- strict thread matches above, loose matches on Subject: below --
2021-10-19 20:09 [yocto-autobuilder-helper][dunfell 0/3] Patch review Steve Sakoman
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=cover.1645543004.git.steve@sakoman.com \
--to=steve@sakoman.com \
--cc=yocto@lists.yoctoproject.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