public inbox for [email protected]
help / color / mirror / Atom feedFrom: Chapman Flack <[email protected]>
To: Kartik Ohri <[email protected]>
Cc: [email protected]
Subject: Re: Starting build-system work (Windows/Mac users please speak up)
Date: Fri, 29 May 2020 14:44:53 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAASLQ4PAQ0PNAxJ5ad9U6o+RT2ip19FXvgoK2y1kGWaJbTZ1WQ@mail.gmail.com>
References: <[email protected]>
<CAASLQ4OdOma6h5Mu=hMEPyk0M4-MomYZLnhGH+2wVoL1vt_UEg@mail.gmail.com>
<[email protected]>
<CAASLQ4P11FFgefy_xK0Tcw3vWt1F1MNyVgK5eU=PFGvYrpZcyw@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
<CAASLQ4PAQ0PNAxJ5ad9U6o+RT2ip19FXvgoK2y1kGWaJbTZ1WQ@mail.gmail.com>
On 05/29/20 13:38, Kartik Ohri wrote:
> 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?
It might be ok to just filter it down to the actual messages and first
stack-trace lines (or maybe actual message, first line and last line of
stack trace), sorted and uniq'd and put into the log, and then allow the
file to go away. If something shows up that is interesting, it will
probably be reproducible in a local run.
I would be more interested in preserving hs_err_pid<n>.log files, but
I think those are less huge, and might just fit in the log.
Regards,
-Chap
view thread (47+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Starting build-system work (Windows/Mac users please speak up)
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox