From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6669723628337102848 X-Received: by 2002:a2e:910d:: with SMTP id m13mr1268096ljg.30.1553068508604; Wed, 20 Mar 2019 00:55:08 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:121d:: with SMTP id t29ls171117lje.4.gmail; Wed, 20 Mar 2019 00:55:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqyxcbUL8SHTP4xSBY23UXa02PAiFFU15xdcsLfcq+0l9QtVPpZ9nu82mjkv4nzg4kxOIkiN X-Received: by 2002:a2e:290:: with SMTP id y16mr1645312lje.20.1553068508093; Wed, 20 Mar 2019 00:55:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553068508; cv=none; d=google.com; s=arc-20160816; b=Idka2/CsiAsxZarExZzetded5t12cQ3A5VhxjIfh/5kkkJnj0GK+0OUSlEt6Nm3LiM /UXyPoC76+PJg227WZOPibWcSbsHRf7w4pboDRD/p1gSVBhmsVvNW/mZD6WjhIv1Qi1v 1psxeCF+mk6by+bW8ty5Hh1knWR0qkFpB0V6VUqsblqnvSd0Mu++IRrCl9wZCqs/H/KY QHbHLMYMaEoWmuT1dzoXiySA2PavLrL2RA/lS/3tTBhF8F+SLHJoTHDncNVSPO0Z7WgG V6gBS3s8Iy25vvpiJM7MQ4sYT3jeV11GuMFbO5ZuTsrTGhxQhOB3lipSZ3MLpu7t94v5 uILw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:organization:from:references:to:subject; bh=M/BuuHLGLp55V1gj+zlC61Q3uax81O1rMJQL04XkP08=; b=yXgAlCHnn25su/iHiWvQsl3iOyfFh15Pipd/NrhrCh5UzKfGwM05icdJVu3wvNNHH3 Q+68UBX2kXVzG+alukSiCsfOfzA3aDYv5IDgmo0xWLR1zXYJ8x0hR2VIPhvRaSO0HDNQ QWQ+miiZO+IEDp1tid5o5SSfBulrVKM4ChIGeoBM0GSmFf2WGjBAAD0ce6PNZRLf45Tq unVGVdJiNk1vr5kGwDluR8N2xDwMiVg1gIRlGUpJdHVTLeROi9GC32IHmhkU2icEGi41 UZrXmEAmUg7dMB9l+d2T1ay0SY/Gja4BudnzekFGqYlh1EaEtLnjTFdj+3TLEWdLC7r0 HEpQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of mosipov@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=mosipov@ilbers.de Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id z15si47083lfe.5.2019.03.20.00.55.07 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 20 Mar 2019 00:55:07 -0700 (PDT) Received-SPF: pass (google.com: domain of mosipov@ilbers.de designates 85.214.156.166 as permitted sender) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of mosipov@ilbers.de designates 85.214.156.166 as permitted sender) smtp.mailfrom=mosipov@ilbers.de Received: from [192.168.50.164] (d51a48a80.access.telenet.be [81.164.138.128]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id x2K7t6el019295 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 20 Mar 2019 08:55:06 +0100 Subject: Re: [PATCH v7 0/5] Fix usage of additional apt keys and repos To: Jan Kiszka , "Andreas J. Reichel" , isar-users@googlegroups.com References: <20190319133523.32456-1-andreas.reichel.ext@siemens.com> <1d5477ce-2bf8-e734-c50a-6281c7d85959@siemens.com> <688943e7-4acc-94a1-810d-00f75fe6a070@ilbers.de> From: "Maxim Yu. Osipov" Organization: ilbers GmbH Message-ID: Date: Wed, 20 Mar 2019 08:55:05 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: E/YwqmXsK/ci Hi Andreas, Jan, On 3/20/19 8:12 AM, Jan Kiszka wrote: > On 20.03.19 07:48, Maxim Yu. Osipov wrote: >> Hi Jan, >> >> On 3/20/19 7:26 AM, Jan Kiszka wrote: >>> On 19.03.19 22:58, Maxim Yu. Osipov wrote: >>>> Hi Andreas, >>>> >>>> CI build ('scripts/ci_build.sh -q') failed. See >>>> http://isar-build.org:8080/job/isar_mosipov_next/165/console >>>> >>> >>> This is the same error I saw yesterday ("..isar-bootstrap-target/rootfs/dev: >>> not mounted"). And given that this and my build had no overlap in our own >>> patches, it must be something else you should examine because it may affect >>> your patches (next..e13be9cefd87). >> >> Yep, when I tested my patches CI build passed OK, >> but now I see the same error in overnight build of 'next'. >> > > OK, that makes more sense again. 1) I've analyzed the two last build failures in 'next' branch - the reason is quite stupid - some of the packages can't be downloaded: For http://isar-build.org:8080/job/isar_next/258/console - libprocps3, for http://isar-build.org:8080/job/isar_next/259/console - ncurses-bin. 2) As for build with Andreas v7 patch seriesthe failure is related to keys stuff (raspbian-jessie-armhf): ERROR: mc:rpi-jessie:isar-bootstrap-target-1.0-r0 do_bootstrap: Function failed: do_bootstrap (log file is located at /workspace/build/isar_mosipov_next/165/build/tmp/work/raspbian-jessie-armhf/isar-bootstrap-target/temp/log.do_bootstrap.12981) ERROR: Logfile of failure stored in: /workspace/build/isar_mosipov_next/165/build/tmp/work/raspbian-jessie-armhf/isar-bootstrap-target/temp/log.do_bootstrap.12981 Log data follows: | DEBUG: Executing shell function do_bootstrap | I: Running command: debootstrap --arch armhf --foreign --verbose --variant=minbase --include=locales,gnupg2,apt-transport-https,ca-certificates --components=main,contrib,non-free,firmware jessie /workspace/build/isar_mosipov_next/165/build/tmp/work/raspbian-jessie-armhf/isar-bootstrap-target/rootfs http://archive.raspbian.org/raspbian | I: Retrieving InRelease | I: Checking Release signature | E: Release signed by unknown key (key id 9165938D90FDDD2E) | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_bootstrap (log file is located at /workspace/build/isar_mosipov_next/165/build/tmp/work/raspbian-jessie-armhf/isar-bootstrap-target/temp/log.do_bootstrap.12981) NOTE: recipe isar-bootstrap-target-1.0-r0: task do_bootstrap: Failed So, Andreas, please have a look on that. Regards, Maxim. >> >>>> We may create project for you on isar-build.org so you can run CI build on >>>> isar-build.org before submitting patches to the mailing list. >>>> We just need your github repo name (like >>>> https://github.com/henning-schild-work/isar/) >>> >>> We rather need to find a way to make CI public, the current state is rather >>> suboptimal. It's also not very well integrated with github. >>> >>> In fact, we need to find a way to build Isar in the cloud in general, also for >>> use cases such as https://gitlab.com/cip-project/cip-core/isar-cip-core. And >>> our internal CI is not scaling either. We do know how to do that better >>> (container-based builds, controlled e.g. by gitlab-ci), but not yet how to >>> deploy economically. >> >> Agreed. To be honest I'm not a big fan of gitlab - it's rather slow. >> Do you have any suggestions regarding other alternatives to gitlab/jenkins? > > The speed of gitlab is primarily a matter of how you deploy it (ok, when you > have >25K users and >40K projects like we do at Siemens, there are also other > limits). But this is about where to run the CI builds and tests and how to make > those results available. > > Unfortunately, our builds take long and require root permissions. So we cannot > simply use any of the public CI services, that scale well but are limited in > those regards. We need hosting in VMs that we control (and likely also pay for), > but that can also be cloned by other users (copy&paste of deployment recipes). > We played with AWS as well as Google Compute and Kubernetes clusters that spawn > up powerful runners on demand (you can afford running them 24/7). These recipes > aren't complete yet, unfortunately, and tuning them takes some time. That's why > this isn't ready yet. I'll try to prioritize that topic as it is becoming a > bottleneck in many projects. > > Jan > -- Maxim Osipov ilbers GmbH Maria-Merian-Str. 8 85521 Ottobrunn Germany +49 (151) 6517 6917 mosipov@ilbers.de http://ilbers.de/ Commercial register Munich, HRB 214197 General Manager: Baurzhan Ismagulov