707632 - make android logs easier to read by not showing the output of the rm cleanup stage

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

when I am debugging android logs, I usually scroll to the bottom and expect to figure out what is going on.  While this is true, I have to scroll for a minute just to get past all the:
========= Started 'rm -rfv ...' (results: 0, elapsed: 15 secs) ==========
rm -rfv build
.
:

This information provides no valuable data to me.

Comment 1

[Mike Taylor [:bear]]

This was done because the clearing of the build/test directories was taking longer than the step timeout when the foopys were very busy.  Now this was also with the original foopy hardware (very old mac minis) so we may be able to revisit this for new foopys

Comment 2

[Chris Cooper [:coop] (he/him)]

(In reply to Mike Taylor [:bear] from comment #1)
> This was done because the clearing of the build/test directories was taking
> longer than the step timeout when the foopys were very busy.  Now this was
> also with the original foopy hardware (very old mac minis) so we may be able
> to revisit this for new foopys

Could we make the rm flags an option so we can toggle verbosity on/off from the configs?

Comment 3

[Justin Wood (:Callek)]

(In reply to Chris Cooper [:coop] from comment #2)
> (In reply to Mike Taylor [:bear] from comment #1)
> > This was done because the clearing of the build/test directories was taking
> > longer than the step timeout when the foopys were very busy.  Now this was
> > also with the original foopy hardware (very old mac minis) so we may be able
> > to revisit this for new foopys
> 
> Could we make the rm flags an option so we can toggle verbosity on/off from
> the configs?

Possibly, though Bug 670199 [when worked on] might reduce disk i/o enough that we can safely remove -v from the rm command all around here.

Comment 4

[[e-mail] (:bhearsum)]

We're not this noisy anymore.