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.
Random failures on Travis and AppVeyor - Failed to request component-reports
See original GitHub issueDescribe the bug
On Travis and AppVeyor - I am seeing my build fail on the Maven goal org.owasp:dependency-check-maven:5.0.0-M3:check with the error Failed to request component-reports. My build consists of 51 modules, and the module it fails on varies from build to build.
** Version of dependency-check used ** Maven plugin version 5.0.0-M3
** Log file **
[ERROR] Failed to execute goal org.owasp:dependency-check-maven:5.0.0-M3:check (default) on project exist-cache: One or more exceptions occurred during dependency-check analysis: One or more exceptions occurred during analysis:
[ERROR] Failed to request component-reports
[ERROR] -> [Help 1]
To Reproduce Run the build here: https://travis-ci.com/eXist-db/exist/builds/111687162 or here https://ci.appveyor.com/project/AdamRetter/exist/builds/24526217/
Expected behavior The plugin should work.
Additional context Tried OpenJDK 8, 9, 10 and Oracle JDK 11. Maven version 3.6.0
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@jeremylong So is this considered fixed in
5.0.0? Our Travis and AppVeyor CI does seem to be passing now 😃 Thanks@jeremylong Would it be possible to make the error message clearer, perhaps if we can detect an HTTP error code when requesting the OSS Index, we could also show that to the user and indicate that the problem is not with your plugin, but rather a network issue?