Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Attempt work around for race-y sort of condition in Selenium sizzle checkers. #3451
I recently discovered you can add little inline non-functional documentation to source code itself that I believe are called comments or something. I have added one of these things to the code to explain the problem and the work around.
I believe this rare condition explains this failing test here - https://jenkins.galaxyproject.org/view/All/job/selenium/54/testReport/junit/selenium_tests.test_stock_tours/TestStockToursTestCase/test_core_history/. This test has never failed for me locally and this is the only time I've seen it fail on Jenkins as well.
The only remaining failures in my latest Jenkins run (post merge of #3450) were these stale errors - https://jenkins.galaxyproject.org/view/All/job/selenium/56/testReport/.
Jan 25, 2017
4 checks passed
I think that helped - but we still seem to have some problems with this in the tour testing. I'll have to look in depth some more.