Mailinglist Archive: yast-devel (100 mails)

< Previous Next >
Re: [yast-devel] Fail fast at Travis?
Dne 27.1.2015 v 12:31 Jiri Srain napsal(a):
On 01/27/2015 11:48 AM, Josef Reidinger wrote:
[...]
Is possible to have it less verbose? all traversing dirs looks useless for
me.

Good idea, I did a test in yast2 package:

- Removed "rake check:syntax" call (useless after adding rubocop check,
the rubocop check fails when there is a syntax error so it's not needed any
more).
It prints status for each file, removing it saves ~250 lines in the output.

- Added "-s" (silent) "make" option, it hides messages like "Entering directory
...",
"Nothing to be done for ...", "Leaving directory ...", which are printed a
lot.

The result is really interesting, the log size has been decreased from
~4600 lines [1] to ~2500 [2], which is a huge difference (almost half of the
original
size!).

I'll open a PR for that change...


Well, what about just to listing the tests which succeed without any
additional
data and only including the details for failed tests in the log?

Um, that would be nice, unfortunately it cannot be implemented easily :-(

The problem is that Travis displays STDOUT + STDERR of the executed script, you
would
need to either change the make/rake behavior (huh...) or add some output
filtering
(that would be non-trivial and probably very sensitive to output format changes
in
rake/make so not really recommended...).


[1] https://travis-ci.org/yast/yast-yast2/builds/48464147
[2] https://travis-ci.org/yast/yast-yast2/builds/48468523

--

Ladislav Slez√°k
Appliance department / YaST Developer
Lihovarsk√° 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
lslezak@xxxxxxxx
SUSE
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups