livy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Saisai Shao <sai.sai.s...@gmail.com>
Subject Re: Making travis logs less verbose
Date Tue, 12 Feb 2019 01:52:14 GMT
Problem is that there's no better way to get detailed log on travis without
printing in out on screen. I was struggling on it when debugging on travis.

Thanks
Saisai

Meisam Fathi <meisam.fathi@gmail.com> 于2019年2月9日周六 下午12:19写道:

> This may do the trick for maven
>
> mvn -Dorg.slf4j.simpleLogger.defaultLogLevel=warn ...
>
> Tanks,
> Meisam
>
> On Fri, Feb 8, 2019 at 2:11 PM Marcelo Vanzin <vanzin@cloudera.com.invalid
> >
> wrote:
>
> > If you know how to silence messages from the setup phase (apt / pip /
> > git), go for it. Those seem kinda hidden by Travis, but maybe there's
> > a setting I'm not familiar with.
> >
> > Maven also has a -B option that makes things a little less verbose in
> > non-interactive terminals. I think -quiet might be a little overkill.
> >
> > On Thu, Feb 7, 2019 at 2:40 PM Meisam Fathi <meisam.fathi@gmail.com>
> > wrote:
> > >
> > > Each build on travis generates 10K+ lines of log. Should we make build
> > > commands less verbose by passing --quiet to them?
> > >
> > > As an example, apt-get installs and pip installs generate 3K+ lines on
> > > their own. Maven generates another 6K+ lines of log, but I am not sure
> if
> > > scilencing maven is a good idea. Passing --quiet to Maven silences
> scalac
> > > warnging.
> > >
> > > Having said all of that, should we make travis logs less verbose? If
> > yes, I
> > > can send a PR.
> > >
> > > Thanks,
> > > Meisam
> >
> >
> >
> > --
> > Marcelo
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message