Test cargo's exponential dependency blowup

Open aleksator opened this issue 5 years ago • 2 comments

There is an issue with cargo not being able to perform dependency resolution in a reasonable time. https://github.com/rust-lang/cargo/issues/8539

Let's see if pubgrub can handle it by creating a test with a similar dependency structure.

Oct 06 '20 11:10 aleksator

This is a grate test case! It will need to wait for us to support most of Cargos features (multiple versions per crate, links attributes, and features) to be sure we are better.

Oct 06 '20 13:10 Eh2406

Indeed we should do that when making a case for inclusion in cargo.

I believe we can still test if we experience the blowup as is. Multiple versions per crate could be emulated by just renaming lib to lib_1 and lib_2 in the dependency tree, and the other 2 probably aren't central to the dependency resolution algorithm.

Oct 06 '20 14:10 aleksator