search

christopherpow / nesicide

Integrated Development Environment for the 8-bit Nintendo Entertainment System
315 stars 38 forks source link

Reduce output of the Travis CI scripts #31

Closed ghost closed 5 years ago

ghost commented 6 years ago

Currently, there is no way to tell what went wrong with the Travis CI builds without downloading the logs. There should be some way to silence the current build script to only give off warnings and errors.

christopherpow commented 6 years ago

I agree, but I'm new to the whole Travis thing and don't have much time to devote to figuring it out. Currently I believe the build is failing because of some Qt incompatibilities within the Travis environment.

christopherpow commented 5 years ago

Travis builds for Linux and OSX are passing now. Travis builds for Windows builds is in progress, not working yet [for Travis community...]. I'm closing this. I will continue to look to reduce log clutter.