fix: actually set parallel to true by default

[dgunay]

Resolves #32

[aaronc]

Seems like there are some tests that fail I'm assuming because they actually don't work in parallel mode (haven't had a chance to check in detail yet). So we need to explicitly disable parallel in those tests.

I wonder if for tagging this release it's okay to just do a minor or patch version bump with a warning that upgrading may break some tests that depended on this bug.

[dgunay]

Seems like there are some tests that fail I'm assuming because they actually don't work in parallel mode (haven't had a chance to check in detail yet). So we need to explicitly disable parallel in those tests.

I wonder if for tagging this release it's okay to just do a minor or patch version bump with a warning that upgrading may break some tests that depended on this bug.

I'll leave that up to you. I've marked the tests non parallel.

In case you aren't aware, the test suite also trips the race detector in several places.

[aaronc]

In case you aren't aware, the test suite also trips the race detector in several places.

Okay, thanks for letting me know! I'll create a separate issue for that. I think let's merge this now, but I want to fix those issues before tagging a new release. It looks like some of these issues could be problematic in parallel execution.