From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6683767157560442880 X-Received: by 2002:a5d:624d:: with SMTP id m13mr1670583wrv.305.1556189895331; Thu, 25 Apr 2019 03:58:15 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a5d:5287:: with SMTP id c7ls3328912wrv.6.gmail; Thu, 25 Apr 2019 03:58:14 -0700 (PDT) X-Google-Smtp-Source: APXvYqzVhpJNTx3R5wNXKs/MgnR3Pbcri7XcXj3ZQF3MVT98Hi/5EUNGNQTUKtoa6twMkwjnCeto X-Received: by 2002:a5d:434c:: with SMTP id u12mr26815720wrr.92.1556189894932; Thu, 25 Apr 2019 03:58:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556189894; cv=none; d=google.com; s=arc-20160816; b=npFnldnbjCmDSQY7/haibtZJLa53nBgG1lo6qSslGg502VioZUvLVHKmvFEN7+pR51 A5glUd3Kp5txL/iXVgTBINCoBn8bCT5tCsQF5mB2ymSNOBvJ7pkxwTZVGTsdOuEFw4eS hmGnr0rZENFXCPVCgZsmEq9Suk8j02WnGlrOO73m8EgovfJ2fzxbfej/QHWf8xYfTzhp Pfe1pEnhKe9Z4nC3whX2jVvFDnGsO+H36SfUKyMtXiqb2ds1Bgz6Qn9+gZcGz6/SYpJR kideWlrVMjRgngSWJWeH4QMHIZ0se/Uq5q2NXkqOosTDJ99FeG9dBk8VugCzPPrD/FcX RvyQ== 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:from:references:to:subject; bh=5olzrfOWesK5OzsP3oQ4RA77Xjr/T1E9aRLyg+sYgZk=; b=FRMKfLp3vOJnccatWXPRouBdyPCTHK1mxIKuEn2bOEu4sTL9IvfZsHFO0tKQVOl72v NIazhrnET9kf1p9jNLT4nzWF9rJGBXUFDbYyfzwVEEl85NP2/PEy2kbMyAbA7yOmCeLx Se3gRfth7egrUj1nU3CdNM5baYfTmUAE6oKsJcc1QEyb7H8Y8NTnV9USEZsEjtX9y+gG VKo6s4jc1nPypyyNA2EHP5BwdQ1pUsA3F1XKrCzdKy2mvfvJBuL90/dOZgYLhFVg4SNx 5gAmHT/mOdfCQsUZkA3rjPYmySeYFcRnNZuaQLn8EG3WuEBolwNZe3DhsroMVzy2VEq0 zaGA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id z185si1281279wmb.0.2019.04.25.03.58.14 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 25 Apr 2019 03:58:14 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id x3PAwEHB030595 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 25 Apr 2019 12:58:14 +0200 Received: from [139.22.38.17] ([139.22.38.17]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x3PAwDRC021588 for ; Thu, 25 Apr 2019 12:58:14 +0200 Subject: Re: Project isar_claudius_ilbers_fast_ci on isar-build.org To: isar-users References: <9563e12a-8b2b-805e-f0a1-ebbf8d82f265@siemens.com> <20190425105433.GK21981@yssyq.m.ilbers.de> From: Jan Kiszka Message-ID: Date: Thu, 25 Apr 2019 12:58:13 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <20190425105433.GK21981@yssyq.m.ilbers.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: 1FwJ6qnecRtr On 25.04.19 12:54, Baurzhan Ismagulov wrote: > On Thu, Apr 25, 2019 at 12:30:58PM +0200, Jan Kiszka wrote: >>> Now I enabled cross-compilation for rpi-stretch locally and now I cannot >>> build next there, but it builds apparently on isar-build... >> >> ...and apparently also on gitlab-ci. > > Do I understand correctly, next does build on gitlab-ci? > It's still running, but it seems to have past the failure points with Claudius' patches applied. > >> So we have a race that probably papers >> over it in larger CI runs. If you can reproduce without that race, please >> debug. > > That might also be a simpler issue like missing host packages. rpi requires > some packages that are not required by other targets. If one doesn't usually > build for rpi, those might be missing. > There are multiple issues, only one of them is in the rpi target. There is generally no way around studying the logs in details. > >>> I would really love to be able to reproduce exactly that issue locally... >> >> Then buy yourself a blade server as laptop ;). Look, not all issues can be >> reproduced locally, at least not before you understood the boundary >> conditions. That's very common and not always the problem of some CI system. > > next should build locally. If there is a problem with the local build, we > shouldn't ignore it. Maybe after this first problem is solved, one can also > reproduce exactly that issue locally. Let's understand the problems first, then do the post-portem analysis why there weren't found early if they could have. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux