Accessing individual logs of failures on the buildbot

[Ryan Schmidt]

On Jan 14, 2016, at 6:29 AM, Mojca Miklavec wrote:

> This is probably not possible at the moment, but maybe there's some
> feasible way to implement it?
> 
> On:
> 
> https://build.macports.org/builders/buildports-snowleopard-x86_64/builds/39756/steps/cleanup/logs/stdio
> 
> one can see the following:
> 
> ./logs-20160113-111820/fail/p5-gimp.log
> ./logs-20160113-111820/fail/p5-musicbrainz-discid.log
> ./logs-20160113-111820/fail/p5-nkf.log
> ./logs-20160113-111820/fail/p5-opengl.log
> ./logs-20160113-111820/fail/p5-sdl_perl.log
> ./logs-20160113-111820/fail/p5-text-chasen.log
> ./logs-20160113-111820/fail/p5-text-kakasi.log
> ./logs-20160113-111820/fail/p5-www-wolframalpha.log
> ./logs-20160113-111820/fail/p5.22-gimp.log
> ./logs-20160113-111820/fail/p5.22-opengl.log
> ./logs-20160113-111820/fail/p5.22-sdl_perl.log
> ./logs-20160113-111820/fail/p5.22-text-kakasi.log
> ./logs-20160113-111820/fail

I assume that's a list of files that were deleted by the cleanup operation.


> Is there any way to access these individual files as opposed to having
> to download and inspect the complete 2.5 GB log file?

I don't think anything is saved from a build run except for the complete logs of each step, and those only for a time.


I would probably suggest forcing a new build of some or all of the ports that failed, then getting that smaller log file.