AltHub team use travis for test code, but sometime test show error, sometime test show that all good.
Repository of code: https://github.com/AltHub-Team/Aurora-Station
Log failed test: https://api.travis-ci.org/v3/job/611385317/log.txt
https://api.travis-ci.org/v3/job/611385319/log.txt
Log succes test: https://api.travis-ci.org/v3/job/611397184/log.txt
ID:2522498
Nov 13 2019, 10:11 am
|
|||||||||||||
Not a bug
| |||||||||||||
I can tell you with confidence that this is a Travis issue and has nothing to do with BYOND.
|
In response to SpaceManiac
|
|
SpaceManiac wrote:
I can tell you with confidence that this is a Travis issue and has nothing to do with BYOND. Cool, thanks. I'll close the issue. |
For the rest of this, I have absolutely no information to go on and nothing to investigate. The log saying "Whoops, something must have gotten stuck" doesn't tell me anything. I need actual output from whichever program was running, or if it hung I would need something from a debugger stopping the process that could tell me where it was currently at and perhaps what its stack trace looked like.
The failure appears to happen in the travis_apt_get_update call but I have no idea what that does or where it could possibly get stuck. For all I know this isn't a BYOND issue at all, and could be a problem with networking or something else.