From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: bug#36684: "View build log" - but it's empty (at first)! Date: Mon, 15 Jul 2019 23:41:06 -0700 Message-ID: <87blxu1ny5.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:33468) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hnHA4-0005M7-11 for bug-guix@gnu.org; Tue, 16 Jul 2019 02:42:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hnHA3-00067w-0L for bug-guix@gnu.org; Tue, 16 Jul 2019 02:42:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:40713) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hnHA2-00067q-Ra for bug-guix@gnu.org; Tue, 16 Jul 2019 02:42:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hnHA2-0002tp-Mj for bug-guix@gnu.org; Tue, 16 Jul 2019 02:42:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Received: from eggs.gnu.org ([2001:470:142:3::10]:33112) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hnH9D-0005FT-MA for bug-guix@gnu.org; Tue, 16 Jul 2019 02:41:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hnH9C-0005DP-LZ for bug-guix@gnu.org; Tue, 16 Jul 2019 02:41:11 -0400 Received: from mail-pg1-x52d.google.com ([2607:f8b0:4864:20::52d]:35522) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hnH9C-0005Cy-Fk for bug-guix@gnu.org; Tue, 16 Jul 2019 02:41:10 -0400 Received: by mail-pg1-x52d.google.com with SMTP id s1so2610657pgr.2 for ; Mon, 15 Jul 2019 23:41:10 -0700 (PDT) Received: from garuda.local ([2601:601:9d80:25b2::d12]) by smtp.gmail.com with ESMTPSA id y22sm17716624pgj.38.2019.07.15.23.41.07 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 15 Jul 2019 23:41:07 -0700 (PDT) List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 36684@debbugs.gnu.org Hi, Sometimes, I see an error like the following (it is not specific to ant-bootstrap): --8<---------------cut here---------------start------------->8--- $ guix package -m ~/profile-packages.scm ... building /gnu/store/76apf0hpcdabpjy0839nhkwgfrz3m8z5-ant-bootstrap-1.8.4.drv... | 'build' phasebuilder for `/gnu/store/76apf0hpcdabpjy0839nhkwgfrz3m8z5-ant-bootstrap-1.8.4.drv' failed with exit code 1 build of /gnu/store/76apf0hpcdabpjy0839nhkwgfrz3m8z5-ant-bootstrap-1.8.4.drv failed View build log at '/var/log/guix/drvs/76/apf0hpcdabpjy0839nhkwgfrz3m8z5-ant-bootstrap-1.8.4.drv.bz2'. cannot build derivation `/gnu/store/3l11fmnyc4k1dcwlijk4vdsq70jc4lqs-icedtea-3.7.0.drv': 1 dependencies couldn't be built killing process 20600 cannot build derivation `/gnu/store/b071r8bm2n01mp50g6r5ghxl0m09akdx-profile.drv': 1 dependencies couldn't be built guix package: error: build of `/gnu/store/b071r8bm2n01mp50g6r5ghxl0m09akdx-profile.drv' failed --8<---------------cut here---------------end--------------->8--- But when I try to view the log file very quickly after getting these messages (within about 1 minute or so), I get: --8<---------------cut here---------------start------------->8--- $ file /var/log/guix/drvs/7f/n896phqyv9r636yhjipa9k4qm7g9ni-evolution-data-server-3.30.2.drv.bz2 /var/log/guix/drvs/7f/n896phqyv9r636yhjipa9k4qm7g9ni-evolution-data-server-3.30.2.drv.bz2: empty --8<---------------cut here---------------end--------------->8--- However, when I come back a few minutes later, mysteriously the file has been populated: --8<---------------cut here---------------start------------->8--- $ file /var/log/guix/drvs/7f/n896phqyv9r636yhjipa9k4qm7g9ni-evolution-data-server-3.30.2.drv.bz2 /var/log/guix/drvs/7f/n896phqyv9r636yhjipa9k4qm7g9ni-evolution-data-server-3.30.2.drv.bz2: bzip2 compressed data, block size = 900k --8<---------------cut here---------------end--------------->8--- Indeed, I was originally going to report that the file was empty, but while I was writing this email, it filled up! Is this behavior expected? I anticipated that the file would be finalized (empty or not) before the helpful message "View built log at ..." was printed, but it seems like that message is proleptic, which makes it a little confusing. -- Chris