From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Zhihang Wei <wzh@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] CI: Add files generated during build by kas to .gitignore
Date: Thu, 27 Nov 2025 17:10:12 +0100 [thread overview]
Message-ID: <888fcf87-f6d7-4db7-8373-360d41b58818@siemens.com> (raw)
In-Reply-To: <da588219-c99b-496a-b695-e23ff34b3f77@ilbers.de>
On 27.11.25 16:48, Zhihang Wei wrote:
>
> On 11/27/25 16:27, 'Jan Kiszka' via isar-users wrote:
>> On 27.11.25 16:24, Zhihang Wei wrote:
>>> During testing/building with kas, files, logs and build results are
>>> downloaded and generated under these directories. Add them to
>>> .gitignore.
>>>
>>> Signed-off-by: Zhihang Wei <wzh@ilbers.de>
>>> ---
>>> .gitignore | 3 +++
>>> 1 file changed, 3 insertions(+)
>>>
>>> diff --git a/.gitignore b/.gitignore
>>> index fff155f1..e65bafc2 100644
>>> --- a/.gitignore
>>> +++ b/.gitignore
>>> @@ -4,3 +4,6 @@ __pycache__
>>> .config.yaml*
>>> .kas_shell_history
>>> build*
>>> +/downloads/
>>> +/sstate-cache/
>>> +/isar-sstate/
>> Err, only if you modified the defaults of kas. Normally, everything is
>> under KAS_WORK_DIR, and that is /build.
Sorry, it's under KAS_BUILD_DIR - KAS_WORK_DIR is . by default, normally
the isar repo then.
>>
>> Jan
>>
> After 778e37f0, /downloads is outside of /build by our kas defaults for
> sharing.
Nope, this is not correct. This commit is using vanilla kas-container
4.8.1, and that does not change DL_DIR or KAS_BUILD_DIR.
> /sstate-cache is created outside /build also for sharing, commit 26c52efc.
> /isar-sstate is by default created outside /build during testing, 20c8a836.
This is correct - but both very ugly. I would recommend directing the
testsuites output into a separate subdir if you don't want to reuse the
standard dir (build) that interactive builds use.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/888fcf87-f6d7-4db7-8373-360d41b58818%40siemens.com.
prev parent reply other threads:[~2025-11-27 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 15:24 Zhihang Wei
2025-11-27 15:27 ` 'Jan Kiszka' via isar-users
2025-11-27 15:48 ` Zhihang Wei
2025-11-27 16:10 ` 'Jan Kiszka' via isar-users [this message]
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=888fcf87-f6d7-4db7-8373-360d41b58818@siemens.com \
--to=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=wzh@ilbers.de \
/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