Actual Behavior

conda_build.utils.get_conda_operation_locks had its signature updated some time ago but one of the calls to it wasn't updated to account for that

55eca10#diff-c54c378feea1d475af4a7c30e9be71e40de70f98c5e804e50e8c676569496f8aL326-R336

Expected Behavior

I think the call should probably look something like this based on what's passed to the get_conda_operation_locks call in conda_build.environ.get_install_actions

locks = utils.get_conda_operation_locks(config.locking, tuple(config.bldpkgs_dirs), config.timeout)

I found this while trying to see if/how conda and conda build prevents race conditions in the package cache and am unsure if it actually causes any issues