Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jeixq-0001qD-KI for pljava-dev@arkaria.postgresql.org; Fri, 29 May 2020 17:38:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jeixp-0003Zb-9N for pljava-dev@arkaria.postgresql.org; Fri, 29 May 2020 17:38:37 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jeixp-0003ZT-1y for pljava-dev@lists.postgresql.org; Fri, 29 May 2020 17:38:37 +0000 Received: from mail-ej1-x62c.google.com ([2a00:1450:4864:20::62c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jeixn-0002by-1l for pljava-dev@lists.postgresql.org; Fri, 29 May 2020 17:38:36 +0000 Received: by mail-ej1-x62c.google.com with SMTP id k11so2847902ejr.9 for ; Fri, 29 May 2020 10:38:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=61GBziYyRa+MJVlu2fH5VwuCoKrdN0qnNipLGD5/s6w=; b=lHB9vg/UD3CN5/XfS8Puin5S8aSQQO5pdgGtvH0o7v6LceFXxMPN2t3EM97gZwZzYE 7/8LkoyuVfCUz1k6NMKWLbz8nsdqcb5+nON+ug2rv9UxUrZ56Htl9FyGHHYn+cZLuiKk VHTB4+fzpPgYl6LMKvjaR8yN7jGo8T2TrrNmyQLahSPj8QqoL02ld5JPQ7slTs6aJ5MM XqC23B69Tfxy10ulACCwyiFxKSZAaw0gInOWm3RC1IW0qSxcg+L0TxImrlLKZlzXB1df 4zCocDw1Nftt45RhPqnGVVxATsqt+NB3Kba0bSbTyLVOiO4PMq+BdhBsanuOpnH1w4Eg +t2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=61GBziYyRa+MJVlu2fH5VwuCoKrdN0qnNipLGD5/s6w=; b=OkJyeaPW+WPbO9/GI/V6MOLX7YUUb440DECIDuOi89nVKaDzsgEwHNrrPWbrH8rGrN Tk2RNkNf0cC47U4zmDxH5pUiighVQYjoDMfImBjeq/HmTtuvDB4kyUJ6wHiKWzJCAEz2 xhZA8AlCKBJpmcYgICV3Tw4kZF9MKWQ/bxc8oUMDRMyJ5gaF2nQFKCBGk9C8/Mq5lYpX ECy+ZeMJUxU2xY6DLEbxJu79nyMsLK9Do9hXLJK6UM1QGI3m4WWXxwZ7r/+iDNbYqx/z NOwMX6IgGv1q3DBo8SPe62PLSmWuwD6gxNcsjm2bLhPINIYbb1L+nCJuVDaM2dIJBpCF zPzw== X-Gm-Message-State: AOAM5326yvjeVkKb6+ELsS9FDiDzd5hpaiLm5Ce/F0/RpHjnUvPcxQSE 3ElbPa17piwZehzBbebWLS/IwByne9LiCbw+VYI= X-Google-Smtp-Source: ABdhPJyKs2EZiqqlNys4rXNsVkG6lvHCyvH3CI3MO231i4K0Rubgei23g53YbZgEZELhPcwDwzeRmbgEYVCK1v10AxQ= X-Received: by 2002:a17:907:9492:: with SMTP id dm18mr8842333ejc.328.1590773913346; Fri, 29 May 2020 10:38:33 -0700 (PDT) MIME-Version: 1.0 References: <5EC17E17.7070002@anastigmatix.net> <5ECED046.3000308@anastigmatix.net> <5ED0FCB0.405@anastigmatix.net> <5ED10C6D.2020000@anastigmatix.net> <5ED10F36.7060304@anastigmatix.net> In-Reply-To: <5ED10F36.7060304@anastigmatix.net> From: Kartik Ohri Date: Fri, 29 May 2020 23:08:22 +0530 Message-ID: Subject: Re: Starting build-system work (Windows/Mac users please speak up) To: Chapman Flack Cc: pljava-dev@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000005e84905a6ccea9e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --00000000000005e84905a6ccea9e Content-Type: text/plain; charset="UTF-8" > > and save the first line and the first 'at' line, and make a sorted, > uniq'd collection of those for the log, and save the original file > to dive into for more details. > Regarding this, Travis does not store any files after a job completes or terminates. It recommends to use an external storage provider like AWS S3 to upload the logs to before the build finishes. Alternatively, I thought we could email the logs as attachment to an email id in case of failures but this might cause a lot of traffic as there at present 19 jobs in a build. What are your thoughts? --00000000000005e84905a6ccea9e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
and save the first line and the first 'at' line,= and make a sorted,
uniq'd collection of those for the log, and save the original file
to dive into for more details.
Regarding this, Travis does not store any files = after a job completes or terminates. It recommends to use an external stora= ge provider like AWS S3 to upload the logs to before the build finishes. Al= ternatively, I thought we could email the logs as attachment to an email id= in case of failures but this might cause a lot of traffic as there at pres= ent 19 jobs in a build. What are your thoughts?=C2=A0
--00000000000005e84905a6ccea9e--