public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] Add simple Containerfile
Date: Fri, 29 Sep 2023 11:37:53 +0200	[thread overview]
Message-ID: <20230929093753.GA364346@pevik> (raw)
In-Reply-To: <87cyy1e35e.fsf@suse.de>

Hi Richie,

...
> > The benefit is that you have not only a clean git repo for the container,
> > but also not touching your working copy directory. But unless nobody else
> > raise any concern, I'm ok with your current proposal.

> Ah I think I see your concern now. It does not touch the directory
> outside the container. It copies everything in first (IDK if it actually
> copies the data if you are doing a local build).

Ah, sorry, of course.

> Note that I tried using a .dockerignore to stop build artifacts being
> copied, but it's not as rich as the .gitignore(s) we have sprinkled
> throughout the LTP.

...
> >> >> +#!/bin/sh -eux
> >> > nit: out of curiosity, why -u (fail unset variables and parameters)?

> >> I find it finds errors in shell scripts or when using them. E.g. typo's
> >> in env variable names. I just include it wherever possible.

> > +1, maybe we should add it to the current ci scripts as well (+ use params
> > instead of setting it via set command, it should work in dash and busybox shell
> > as well).

> Yeah, I think it should be the default.

I add it at least to the original scripts in ci directory, it should be safe
here. I'll test tst_test.sh and tst_net.sh and send a patch for this.

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2023-09-29  9:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 10:44 [LTP] [PATCH] Add simple Containerfile Richard Palethorpe via ltp
2023-09-28 18:11 ` Petr Vorel
2023-09-29  7:42   ` Richard Palethorpe
2023-09-29  8:15     ` Petr Vorel
2023-09-29  9:15       ` Richard Palethorpe
2023-09-29  9:37         ` Petr Vorel [this message]
2023-10-04 12:28 ` Marius Kittler
2023-10-05  8:07   ` Richard Palethorpe
2023-10-10 11:28 ` Andrea Cervesato via ltp

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=20230929093753.GA364346@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=rpalethorpe@suse.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