From: Philipp Ittershagen <pit@shgn.de>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [RFC PATCH] test: add devel/test-in-docker.sh
Date: Fri, 19 Aug 2016 16:03:15 +0200 [thread overview]
Message-ID: <8760qwc0v0.fsf@pipc.ddns.lcl> (raw)
In-Reply-To: <m2d1l427hf.fsf@guru.guru-group.fi>
Tomi Ollila <tomi.ollila@iki.fi> writes:
> On Wed, Aug 17 2016, Tomi Ollila <tomi.ollila@iki.fi> wrote:
>
>> With this user can try and test notmuch in docker container,
>> in fixed environment where it should compile and tests should pass...
>>
>> Currently provided container environments are Debian 8.5 and
>> Ubuntu 16.04 based. Host OS could be any Linux environment with
>> modern enough docker; Perhaps this works on macOS (with docker 1.12+)
>> too (in Windows this script probably fails).
>> ---
>>
>> Currently quite a few tests FAIL -- due to missing prerequisite tests.
>> It would be easy to add some packages, like gdb, emacs(-nox), dtach,
>> but I left those out just to tease you >;)
>>
>
> There are 2 problems in this script
>
> 1) If the initial docker images (ubuntu:16.04 or debian:8.5) are not
> pulled before docker build started, using sha256 hash of the docker
> image doesn't work as the initial image where to start building on.
>
> 2) Surprisingly(*) ubuntu:16.03 sha256 has changed from
> 42118e3df429f09ca581a9deb3df274601930e428e452f7e4e9f1833c56a100a to
> f8d79ba03c00bbcd8079cf05b7526ac8f4f422744aad8c3747a29a38ed8c4a41
> between 2016-08-15 (mon) and 2016-08-19 (fri).
>
> So, currently `docker pull debian:8.5` and then
> `./test-in-docker debian8` should work. If ubuntu:16.04 was pulled early
> enough `./test-in-docker ubuntu1604` would work (too).
>
> The next version (which I probably do sometime in distant future, when I
> have time to enchange tests (before that I try to do some reviews!)) will
> probably work the opposite way -- use name:tag as source and after build
> spit a (friendly) WARNING if the hash of the initial image has changed
> in-between.
>
>
> (*) or perhaps not so surprisingly -- anyway it is unfortunate that these
> images are not so ephemeral as one would wish for...
>
>
> Tomi
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> https://notmuchmail.org/mailman/listinfo/notmuch
--
Philipp Ittershagen
Senior Researcher
OFFIS e.V. - Institut für Informatik
FuE Berech Verkehr | R&D Division Transportation
Escherweg 2 - 26121 Oldenburg - Germany
Phone/Fax: +49 441 9722-715 / -278
E-Mail: philipp.ittershagen@offis.de
URL: http://www.offis.de/
Registergericht: Amtsgericht Oldenburg VR 1956
Vorstand: Prof. Dr.-Ing. Wolfgang H. Nebel (Vorsitzender),
Prof. Dr. techn. Susanne Boll-Westermann,
Prof. Dr. Werner Damm, Prof. Dr.-Ing. Andreas Hein,
Prof. Dr. Sebastian Lehnhoff
prev parent reply other threads:[~2016-08-19 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 21:07 [RFC PATCH] test: add devel/test-in-docker.sh Tomi Ollila
2016-08-19 13:50 ` Tomi Ollila
2016-08-19 14:03 ` Philipp Ittershagen [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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760qwc0v0.fsf@pipc.ddns.lcl \
--to=pit@shgn.de \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).