add debug information to travis build #1334
Conversation
|
there has been a travis update that might have caused this error |
|
The develop branch now fails in the same way: the "numpy dev" build fails silently after the conda install. From what I see from the debug lines ou activated, it seems related to the ci-helper calling clear_console. |
|
clear_console is not part of the ci-helper scripts. But the scripts seem to exit with 1 for some reason now. |
|
also there was no update of the ci-helper scripts for almost a month. This all worked fine until yesterday |
|
Great the build stops and fails when the logout script on travis is getting called. So from the ci-helpers side everything is OK. |
|
OK removing the logout script lets this test pass again. But since this is a privacy feature maybe we shouldn't do that. I send a support ticket to Travis already earlier today. I'm waiting for a reply and then inform them about what I found out today. |
|
Hello there 👋 The error you are seeing was not caused by #1334 (comment) as you are on our container-based infrastructure and we made updates only to full VM images. The last build log url had logs that cut off, but we're looking into them in more depth to see why the logout script made the build fail. |
|
@kain88-de can we remove the cron job from our travis runs for the time being? It's pretty annoying to get the red "tests do not pass" everywhere even though it's not really the code's fault. |
|
@orbeckst sure you can deactivate the test for the time being |
|
This should be fixed now in upstream |
|
Yes, the cron job build passed (well, installed and did not fail with an error as previously). Another job stalled so I restarted. But it seems indeed that the travis cron job failure has been eliminated. Do you want to revert 429795a ? |
The cron job build seems to fail currently. I'm not sure why that is there is also no indication in the travis log. So lets see what information we get if we add more debug info in the logs.