question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

TravisCI Build Fails

See original GitHub issue

There seems to be something broken in the TravisCI build tests. I discovered an issue in test 4 for detections.findstars.py where suddenly Sphinx didn’t like the multiply defined URLs so submitted #828 thinking that was an easy fix to replace the slightly tidier format for referencing daofind and starfind with anonymous URLs.

However, that subsequently uncovered an issue with TravisCI test 6 (ASTROPY_VERSION=development EVENT_TYPE='pull_request push cron') where any test that goes through astropy.modeling.core hits an astropy deprecation warning (astropy.utils.exceptions.AstropyDeprecationWarning: This function is no longer needed, directly use `inspect.Signature`.) which TravisCI interprets as an error and the build fails.

It seems kinda coincidental to me that both errors mysteriously happened at the same time, so I suspect that my PR #828 might not be necessary if whatever deeper build failure is fixed, but it is available if necessary (or if the error persists after this bigger astropy bug is solved). I don’t know enough about the astropy deprecation system to know what’s causing the second warning (turned error) message, however.

Can we just put a flag somewhere to ignore that warning, or turn warnings back into warnings and not failing errors?

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
pllimcommented, Apr 24, 2019

It is fixed upstream. I think this can be closed.

1reaction
larrybradleycommented, Apr 24, 2019

Yes, it’s due to ~~https://github.com/astropy/astropy/pull/8408.~~ I’m working on a fix.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Common Build Problems - Travis CI Docs
One possible cause for builds failing unexpectedly can be calling set -e (also known as set errexit ), either directly in your .travis.yml...
Read more >
Github - Failure: The Travis CI build failed - Stack Overflow
Your build is failing, so something is wrong (unit tests?) as @osowskit said. Please paste your logs from travis (yes, it probably will...
Read more >
I don't know how to tackle "The Travis CI build failed"
I am facing some problem with My PR approval The Travis CI build failed which I have never experienced before (maybe its with...
Read more >
Erratic build failure without any error · Issue #8920 · travis-ci ...
I'm having this problem - here's an example where two different runs on the same code have different build failures, with no error...
Read more >
Build shows as successful even though the sole job failed
Travis CI - Test and Deploy Your Code with Confidence. Hi folks. I have a build with a test that I've deliberately broken....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found