Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RobotsAndSitemapTest fails at random times #147

Open
aecio opened this issue Dec 4, 2017 · 0 comments
Open

RobotsAndSitemapTest fails at random times #147

aecio opened this issue Dec 4, 2017 · 0 comments
Labels
Milestone

Comments

@aecio
Copy link
Member

aecio commented Dec 4, 2017

Integration test RobotsAndSitemapTest is non-deternministic and fails at times in the continuous integration server. Example stacktraces:

focusedCrawler.integration.RobotsAndSitemapTest > test1ToNotToDownloadSitesDisallowedOnRobots FAILED
    java.lang.AssertionError: URL=http://127.0.0.1:1234/disallowed-link-1.html
    Expected: is not a value less than <0.0>
         but: was <-149.0>
        at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
        at org.junit.Assert.assertThat(Assert.java:956)
        at focusedCrawler.integration.RobotsAndSitemapTest.assertWasNotCrawled(RobotsAndSitemapTest.java:173)
        at focusedCrawler.integration.RobotsAndSitemapTest.test1ToNotToDownloadSitesDisallowedOnRobots(RobotsAndSitemapTest.java:122)
focusedCrawler.integration.RobotsAndSitemapTest > test1ToNotToDownloadSitesDisallowedOnRobots FAILED
    java.lang.AssertionError: URL=http://127.0.0.1:1234/disallowed-link-1.html
    Expected: is not a value less than <0.0>
         but: was <-101.0>
        at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
        at org.junit.Assert.assertThat(Assert.java:956)
        at focusedCrawler.integration.RobotsAndSitemapTest.assertWasNotCrawled(RobotsAndSitemapTest.java:173)
        at focusedCrawler.integration.RobotsAndSitemapTest.test1ToNotToDownloadSitesDisallowedOnRobots(RobotsAndSitemapTest.java:122)
@aecio aecio added this to the 0.10 milestone Dec 4, 2017
@aecio aecio modified the milestones: 0.10, next Feb 1, 2018
@aecio aecio added the bug label Jan 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant