From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6738428500576829440 X-Received: by 2002:a5d:568a:: with SMTP id f10mr7781329wrv.215.1571139085919; Tue, 15 Oct 2019 04:31:25 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:adf:e90e:: with SMTP id f14ls6777944wrm.7.gmail; Tue, 15 Oct 2019 04:31:25 -0700 (PDT) X-Google-Smtp-Source: APXvYqxLy0kzxT6vQQYJIUozc8zr0vw/Vs9us4NUiTtn62urUgXIgPJHNHB0QVl4D1r6UnPYOgnd X-Received: by 2002:adf:dc83:: with SMTP id r3mr30175733wrj.335.1571139085368; Tue, 15 Oct 2019 04:31:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571139085; cv=none; d=google.com; s=arc-20160816; b=dlEHApQFtQjgDXjPb4aVInD4kKfFypxqc/O5oaRGoNx3j0P/I8Lyg+7yc9gQVlmK5J KawDbXWkdgb8CIJ1eISLj43QlbUU3u4Rt26ZB6orfZL98et6HBPNtiEZSQiXgGNk17uq XTpmDpKSkRBURI4pBOTO21AYz9BzBWRqQpyarL/mDRELKm6DK1fxNaPKveRn8I/T6ymG +9TpmWdcxEBtXFWycLhQgA2PMYSS/siUOXcLf2mumf7l0qWBTYRC4DZiw1Qze8ei8vMw 8grFRpp5S4wfSQ5goSQOeQ/7sIyMmVp6ZFNRFP/vJEj+Wq+PrFjjfdC97GvBuuTOpuHQ 1ktg== 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:cc:references:to:subject; bh=hMIkEJUCp+XkF6+ASl+CVgTT0zCKLzZbEaQGWcqdDRc=; b=hRGqjI4FEQXIaZfLw5/nN/jxH1N5rfGsFMoVA6Dh/i+wDesnyeZ2hp79cYfZ0Dgng8 d/S1pqLG0vKDcQQewaP3H9Nl+eq5CpMIemXb4+GBsKCzmz6WUoAIAzIrsGxrWffV+Tkn ds6cJY5H61vz0T0Q5Mokc1lcNb0Xb6imfsnBsdEdQS7aMhtqSOXzWG8BcNkiYN3xF1oK j6DqDGfRchCGqgswpgy2N0cZpkV/k2B7dgNV5aJwfUZDUWY4pOvAfa0wPLOeHdcwmoSA PBAlx/lYOZjCzh1XWjnF/HSuqE6t9842xDv3mhVmSKcOcG+Ll6hg3uGGh3IXuwvov+1q KcCA== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id u15si1147928wmc.1.2019.10.15.04.31.25 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Oct 2019 04:31:25 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id x9FBVOTC024039 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 15 Oct 2019 13:31:25 +0200 Received: from [139.25.68.37] ([139.25.68.37]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x9FBVOhT017763; Tue, 15 Oct 2019 13:31:24 +0200 Subject: Re: [PATCH 2/3] CI: make gitlab-ci build verbose instead of quiet To: Baurzhan Ismagulov References: <20190919170403.21809-1-henning.schild@siemens.com> <20190919170403.21809-3-henning.schild@siemens.com> <32a6c1e3-5028-df8a-8127-ea1828082c29@siemens.com> <20191015104844.a6eodbfewfq23lqa@yssyq.m.ilbers.de> Cc: isar-users@googlegroups.com From: Jan Kiszka Message-ID: <1601e8f5-8219-f7f8-b687-dd21955de6fa@siemens.com> Date: Tue, 15 Oct 2019 13:31:24 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 MIME-Version: 1.0 In-Reply-To: <20191015104844.a6eodbfewfq23lqa@yssyq.m.ilbers.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: QhEl6cESZYrj On 15.10.19 12:48, Baurzhan Ismagulov wrote: > On Sat, Sep 21, 2019 at 12:36:39PM +0200, Jan Kiszka wrote: >>> - - scripts/ci_build.sh -q -f >>> + - scripts/ci_build.sh -f > ... >> NACK, at least until non-verbose mode is fixed to not interleave the output >> of parallel tasks. > > I've enabled that on ci.isar-build.org, since it's the only way to see the > concurrency. This may help debugging sporadic races. I agree that the output is > very hard to read. Sigh... If you really think you can read anything out of the resulting logs in practice (I seriously doubt this), please confine this to your private Jenkins runs. For gitlab-ci, we neither need this - because of [1] - nor is it desired as I explained clearly. Believe me, I've debugged a number of races seen in CI originally just recently. Thanks, Jan > > IIRC, I had a discussion with DEBOS (?) people regarding the logs, but we > didn't go into depth. One approach could be to always log everything (even > messages that don't go to the console), e.g. into a database (with timestamps, > task name and number, etc.), and have a tool to display and filter the output. > > With kind regards, > Baurzhan. > [1] https://github.com/ilbers/isar/commit/e5b7d62f91b233f85361d49871cf9a3dad5b2436 -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux