public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Moessbauer, Felix" <felix.moessbauer@siemens.com>
Subject: Re: [PATCH v2 0/4] Fix ccache issues
Date: Thu, 30 Mar 2023 10:37:14 +0300	[thread overview]
Message-ID: <3485605.dWV9SEqChM@hp> (raw)
In-Reply-To: <9c4580332e0520197ed589f26af61c89ca8bb955.camel@siemens.com>

In mail from Wednesday, 29 March 2023 15:43:10 +03 user Moessbauer, Felix 
wrote:
> On Tue, 2023-03-28 at 18:56 +0300, Uladzimir Bely wrote:
> 
> > In mail from Tuesday, 28 March 2023 18:51:58 +03 user Moessbauer,
> > Felix wrote:
> > 
> > > On Mon, 2023-03-27 at 08:27 +0300, Uladzimir Bely wrote:
> > > 
> > > 
> > > > In mail from Monday, 13 February 2023 10:56:07 +03 user Anton
> > > > Mikanovich 
> > > > wrote:
> > > > 
> > > > 
> > > > > This patchset just fixes some ccache-related issues which
> > > > > prevented
> > > > > us
> > > > > from enabling ccache globally.
> > > 
> > > 
> > > 
> > > Hi,
> > > 
> > > since this commit, I again see ccache issues when mixing cross and
> > > non-
> > > cross compilation for arm64 targets:
> > > 
> > > ccache: error: Failed to create directory /ccache/a/7: Not a
> > > directory
> > > 
> > > The error happened in the non-cross recipe.
> > > 
> > > I'm not 100% sure if this is related, but with ISAR f95f69d3 I did
> > > not
> > > observe these on the same layer.
> > > 
> > > Felix
> > > 
> > 
> > 
> > Probably, it's related to patch2.
> > 
> > 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.
> 

Yes, it sounds a bit challenging. 

Returning back to root-owned ccache would not be a good solution. But if there 
are no other ways to deal with it, we might have to do it.

Alternatively, kas-based downstreams using old isar could apply patch2 as isar 
patch, until updated.

> 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.
> 
> Felix
> 
> 
> 
> > 
> > 
> 
> 





  reply	other threads:[~2023-03-30  7:37 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 [this message]
2023-04-02 18:44         ` Baurzhan Ismagulov
2023-04-05 11:56           ` Moessbauer, Felix
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=3485605.dWV9SEqChM@hp \
    --to=ubely@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --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