Abnormal test running time for consider-using-join test file

[PCManticore]

Steps to reproduce

1. run pytest pylint -k consider_join
2. Watch how the test runs for a couple of seconds

Current behavior

The given test triggers abnormal performance behaviour for a particular check (doesn't seem to be consider-using-join as I disabled that one and it was still taking too many seconds to complete)

Expected behavior

For the test to complete faster than that.

pylint --version output

master

[sushobhit27]

yup it takes around 20 sec, way more than other test cases.
Is it because of redundant test cases, e.g below 3 test cases seems similar

https://github.com/PyCQA/pylint/blob/18023f050f9db7d63df38ab0d18072b60aabee24/pylint/test/functional/consider_join.py#L43

https://github.com/PyCQA/pylint/blob/18023f050f9db7d63df38ab0d18072b60aabee24/pylint/test/functional/consider_join.py#L47

https://github.com/PyCQA/pylint/blob/18023f050f9db7d63df38ab0d18072b60aabee24/pylint/test/functional/consider_join.py#L105

[brycepg]

reusing the name result is causing a 20000 possible inference values, similar to pylint-dev/astroid#579. I've reduced test time from 16s to 2.26s by limiting possible results to 100

[PCManticore]

Thanks @sushobhit27 and @brycepg That's a crazy performance improvement! Nice! Looking forward to see how it's going to affect other topic-performance issues.