Closed mestia closed 6 years ago
Hmmm. Works for me. Which version of falcon (and SHA1) and of pytest (I used 3.3.1)?
Oh, sorry. We are no longer mirroring our internal FALCON repo here. In fact, I think this Issues board will disappear soon too, in favor of pbbioconda. So I think your source-code is way out of date. Unfortunately, my hands are tied.
I have checked pbbioconda rules that are pointing to something that is named falcon. The latest version there is 2.1.0 while the falcon repository here has the latest version 2.1.4. This does not really look as if it were way out of date - but may be I've found the wrong successor of this code. In general BioConda is doing nothing else than Debian - they are packaging source code. So if you somehow distribute the source code we can point our tools to the latest version you want to be distributed by any distributor - be it BioConda, Debian and its derivatives or other Linux or BSD distributions. The restriction to BioConda only seems on one hand artificial and on the other hand not the best way to spread Pacific Biosciences software to the community. I'm aware about the popularity of BioConda but integration into a distribution like Debian is something that is orthogonal to the single user installation by BioConda and you would waste feedback like this kind of reports here if you apply that restriction actively.
We use pb-falcon
. Some other user created falcon
.
Source-distributions are available (for now) in pypeFLOW releases, which are used by the pb-falcon
bioconda recipe.
The pb-assembly
bioconda should have everything you need, though you may need to avoid installing that errant falcon
recipe.
Hi Christopher, thanks for this helpful information. Andreas.
Trying to build falcon I see pytest failures. The first problem and the solution is described here: https://github.com/pytest-dev/pytest/issues/3518
I tried to solve this issue by removing
@pytest.yield_fixture
fromFALCON/test/test_util_system.py
But after that 4 tests still fail:Any hint on how to fix that?