From: | Chapman Flack <chap(at)anastigmatix(dot)net> |
---|---|
To: | Kartik Ohri <kartikohri13(at)gmail(dot)com> |
Cc: | pljava-dev(at)lists(dot)postgresql(dot)org |
Subject: | Re: Starting build-system work (Windows/Mac users please speak up) |
Date: | 2020-05-29 18:44:53 |
Message-ID: | 5ED15825.9060504@anastigmatix.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg토토 꽁 머니SQL : Postg토토 꽁 머니SQL 메일 링리스트 : 2020-05-29 이후 Pljava-Dev 18:44 |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Kartik Ohri | 2020-05-30 08:35:27 | Re: Starting build-system work (Windows/Mac users please speak up) |
Previous Message | Kartik Ohri | 2020-05-29 17:38:22 | Re: Starting build-system work (Windows/Mac users please speak up) |