public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"ibr@radix50.net" <ibr@radix50.net>
Subject: Re: [PATCH v2 0/4] Fix ccache issues
Date: Wed, 5 Apr 2023 11:56:53 +0000	[thread overview]
Message-ID: <f3fe0325298b33cf1f15bb6edd1e59e03be1ad78.camel@siemens.com> (raw)
In-Reply-To: <ZCnNFv8Q2HsEaglJ@ilbers.de>

On Sun, 2023-04-02 at 20:44 +0200, Baurzhan Ismagulov wrote:
> On 2023-03-29 12:43, Moessbauer, Felix wrote:
> > > You might have /ccache/a/ created earlier by 'root', and not it
> > > can't
> > > create a 
> > > subdir as sbuild user.
> > 
> > Hi, this could very well be the case. However, when running in a CI
> > on
> > a project with multiple branches (e.g. during feature integration),
> > this situation cannot be avoided. The cache is shared across all
> > builds
> > of a single project, but these builds might use different ISAR
> > versions.
> > 
> > This technically means, we need to update all branches of the
> > project
> > in a lockstep to be able to re-enable the ccache.
> > 
> > It would be good if we could find a way to avoid this situation.
> 
> What about sudo addgroup ccache; sudo adduser build ccache; sudo
> chgrp -R
> ccache /ccache; sudo chmod -R g+w /ccache; find /ccache -type d |sudo
> xargs
> chmod g+s? Maybe also sudo adduser root ccache.

This would solve the permission issues at the cost of always touching a
lot of files. Especially in case the cache is on a NFS, this could be
problematic. All that boils down to the following root causes:

- shared caches across ISAR versions in the same CI
- inconsistent users creating / accessing the cache in ISAR (e.g.
sbuilder as builder, devshell as root)

Also some custom tasks might accidentally use the ccache and break the
build for the following (possibly unrelated) tasks. I don't know which
solution is best. Ideas are highly appreciated.

Felix

> 
> With kind regards,
> Baurzhan
> 


  reply	other threads:[~2023-04-05 11:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13  7:56 Anton Mikanovich
2023-02-13  7:56 ` [PATCH v2 1/4] ccache: fix dirs creation Anton Mikanovich
2023-02-13  7:56 ` [PATCH v2 2/4] ccache: fix CCACHE_DIR owner for sbuild Anton Mikanovich
2023-02-13  7:56 ` [PATCH v2 3/4] meta: unify cross selection Anton Mikanovich
2023-02-13  7:56 ` [PATCH v2 4/4] ccache: separate cache based on cross compile Anton Mikanovich
2023-02-13  8:01 ` [PATCH v2 0/4] Fix ccache issues Anton Mikanovich
2023-03-27  5:27 ` Uladzimir Bely
2023-03-28 15:51   ` Moessbauer, Felix
2023-03-28 15:56     ` Uladzimir Bely
2023-03-29 12:43       ` Moessbauer, Felix
2023-03-30  7:37         ` Uladzimir Bely
2023-04-02 18:44         ` Baurzhan Ismagulov
2023-04-05 11:56           ` Moessbauer, Felix [this message]
2023-04-05 13:28             ` Baurzhan Ismagulov
2023-04-10  5:44               ` Moessbauer, Felix

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=f3fe0325298b33cf1f15bb6edd1e59e03be1ad78.camel@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=ibr@radix50.net \
    --cc=isar-users@googlegroups.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