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

Disable tool shed test function that fails frequently on Jenkins. #3819

Merged
merged 1 commit into from Mar 29, 2017

Conversation

Projects
None yet
5 participants
@jmchilton
Copy link
Member

commented Mar 27, 2017

xref #1617

@nsoranzo

This comment has been minimized.

Copy link
Member

commented Mar 27, 2017

Maybe that's solved now by #3814?

@mvdbeek

This comment has been minimized.

Copy link
Member

commented Mar 27, 2017

I think there could be a chance that #3814 fixed this, maybe we can observe this for a little longer?

@jmchilton

This comment has been minimized.

Copy link
Member Author

commented Mar 27, 2017

Cool beans - very nice - I'll close and just re-open if I see it on a new PR.

@jmchilton jmchilton closed this Mar 27, 2017

@mvdbeek mvdbeek reopened this Mar 29, 2017

@jmchilton

This comment has been minimized.

Copy link
Member Author

commented Mar 29, 2017

Thanks for re-opening and following up on this @mvdbeek. I check the parent commit and it looks like her branched that work after your PR was merged - so it looks like the bug in the test case (or Galaxy) still exists.

@martenson martenson merged commit ab11adf into galaxyproject:dev Mar 29, 2017

5 checks passed

api test Build finished. 271 tests run, 0 skipped, 0 failed.
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
framework test Build finished. 140 tests run, 0 skipped, 0 failed.
Details
integration test Build finished. 25 tests run, 0 skipped, 0 failed.
Details
toolshed test Build finished. 579 tests run, 0 skipped, 0 failed.
Details
@davebx

This comment has been minimized.

Copy link
Contributor

commented Mar 29, 2017

I've spent quite a number of cycles on trying to track down the cause of that issue, I've so far only been able to determine that it seems to happen on every second run. Don't know if that is of any help, and at my decrepit old age, I'm not even sure my memory is accurate on that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.