Currently, the logging breaks in CI environments.
�[2K�[1GProgress going on 0.01s: preparations�[2K�[1GProgress going on 0.01s: preparations�[2K�[1GProgress going on 0.02s: processing�[2K�[1GProgress going on 0.02s: processing�[2K�[1GProgress going on 0.03s: processing�[2K�[1GProgress going on 0.04s: create jar�[2K�[1GProgress going on 0.04s: create jar�[2K�[1GSuccess in 0.05s: bundler done�[2K�[1GSuccess in 0.05s: bundler done
This is because the log is written to a file and not to a console. While the log is written to a file, it should not be interactive, but just show the result.
Currently, the logging breaks in CI environments.
�[2K�[1GProgress going on 0.01s: preparations�[2K�[1GProgress going on 0.01s: preparations�[2K�[1GProgress going on 0.02s: processing�[2K�[1GProgress going on 0.02s: processing�[2K�[1GProgress going on 0.03s: processing�[2K�[1GProgress going on 0.04s: create jar�[2K�[1GProgress going on 0.04s: create jar�[2K�[1GSuccess in 0.05s: bundler done�[2K�[1GSuccess in 0.05s: bundler doneThis is because the log is written to a file and not to a console. While the log is written to a file, it should not be interactive, but just show the result.