I'm ok with the upgrade, but the environment is quite painful, I fixed lots
of issues due to changes of travis basic image. So I think the upgrade may
introduces several additional changes.
I cannot remember why two mvn builds are required, maybe you can take a try.
Thanks
Saisai
Meisam Fathi
I noticed a couple other things in .travis.yml, but I am not sure why they
are needed.
- The base image is ubuntu:trusty. Can we update it to a later LTS
version of ubuntu like Xenial?
- Travis builds Livy twice: Is there a reason why two mvn builds are
needed?
install: - mvn $MVN_FL
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 于2019年2月9日周六 下午12:19写道：
> This may do the trick for maven
>
> mvn -Dorg.slf4j.simpleLogger.defaultLogLevel=warn ...
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
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
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 li
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.
