-
Notifications
You must be signed in to change notification settings - Fork 145
Pytest Failing (eth2spec not found, Namespace has no attribute, import file mismatch) #1218
Comments
@ChihChengLiang @NIC619 do you see the error above w/ the duplicate test name? i'd suggest we just rename one of them, iirc we had this problem before |
@wschwab have you tried running the eth2 tests after you have the fixtures installed? i'm having some trouble replicating that error w/ |
I didn't see this error when running pytest locally. |
I do, with plain |
Ah, ... I saw it now. My eyes 🙈 |
@ralexstokes Sorry, just got back around to this.
Could you explain what you mean by 'the fixtures'? |
@wschwab yep, i mean the cross-client consensus tests we have in place for both eth1 and eth2. the things that are installed as git submodules, e.g. so generally, you'll do a fresh clone of the repo and then do a submodule initialization which will pull down even more test data we use for cross-client compatibility. once you have all of this then you should be able to run any test |
Thanks for explaining. |
@wschwab pretty sure you need to do an explicit re-pinging @lithp re: the @ChihChengLiang @NIC619 did we ever fix the duplicate test name? |
Yeah, sorry about the |
@ralexstokes The duplicate test name issue is addressed. |
@wschwab i think we have addressed all of the above issues on the remote's end... want to try again and report what you find? |
Sorry for the delay - I've been a bit swamped. Strange. I did a pull to update
|
looks like an issue w/ the fixtures data? what is the output of |
|
and you do have the files under |
Maybe this is the issue? At least in the top directory I have |
@wschwab sorry! typo, it is just you could move to another directory and try a fresh clone/install to see if you have some local state that is botching things? |
On it. I also suspect that this is a local issue. |
Okay. Fresh install turns up a new bug during collection:
poking around in the codebase suggests that
This was found running the whole suite (plain old |
The thread seems to have gone stale - as the main issue is most likely resolved, if there's no response here, I'll close the issue. |
@wschwab i think we are good to close :) if you are still having issues w/ installation, feel free to move to the gitter channel for |
python --version
): Python 3.7.3pip freeze
):aiohttp==3.6.0
alabaster==0.7.12
apipkg==1.5
argcomplete==1.10.0
argh==0.26.2
asn1crypto==1.0.1
async-exit-stack==1.0.1
async-generator==1.10
async-lru==0.1.0
async-timeout==3.0.1
asyncio-cancel-token==0.2.0
atomicwrites==1.3.0
attrdict==2.0.1
attrs==19.2.0
Babel==2.7.0
backcall==0.1.0
base58==1.0.3
bleach==3.1.0
bloom-filter==1.3
bumpversion==0.5.3
cached-property==1.5.1
cachetools==3.1.1
certifi==2019.9.11
cffi==1.12.3
chardet==3.0.4
Click==7.0
coincurve==10.0.0
colorama==0.4.1
coverage==4.5.4
cryptography==2.6.1
cytoolz==0.10.0
decorator==4.4.0
docopt==0.6.2
docutils==0.15.2
eth-abi==1.3.0
eth-account==0.2.3
eth-bloom==1.0.3
eth-hash==0.2.0
eth-keyfile==0.5.1
eth-keys==0.2.4
eth-rlp==0.1.2
eth-typing==2.1.0
eth-utils==1.7.0
execnet==1.7.1
factory-boy==2.11.1
Faker==2.0.2
fastecdsa==1.7.4
flake8==3.5.0
flake8-bugbear==18.8.0
hexbytes==0.2.0
hypothesis==4.40.0
idna==2.7
ifaddr==0.1.6
imagesize==1.1.0
incremental==17.5.0
ipython==7.8.0
ipython-genutils==0.2.0
jedi==0.15.1
Jinja2==2.10.3
jsonschema==3.0.1
lahja==0.14.5
libp2p==0.1.1
lru-dict==1.1.6
lxml==4.4.1
MarkupSafe==1.1.1
mccabe==0.6.1
milagro-bls-binding==0.1.3
more-itertools==7.2.0
multiaddr==0.0.8
multidict==4.5.2
mypy==0.730
mypy-extensions==0.4.2
netaddr==0.7.19
netdisco==2.6.0
netifaces==0.10.9
outcome==1.0.0
packaging==19.2
parsimonious==0.8.1
parso==0.5.1
pathtools==0.1.2
pexpect==4.7.0
pickleshare==0.7.5
pkginfo==1.5.0.1
pluggy==0.7.1
plyvel==1.0.5
prompt-toolkit==2.0.10
protobuf==3.9.0
ptyprocess==0.6.0
py==1.8.0
py-ecc==1.7.1
py-evm==0.3.0a7
pycodestyle==2.3.1
pycparser==2.19
pycryptodome==3.9.0
pyethash==0.1.27
pyflakes==1.6.0
Pygments==2.4.2
pymultihash==0.8.2
pyparsing==2.4.2
pyrsistent==0.15.4
pysha3==1.0.2
pytest==3.6.4
pytest-aiohttp==0.3.0
pytest-asyncio==0.10.0
pytest-cov==2.5.1
pytest-mock==1.10.4
pytest-randomly==3.0.0
pytest-trio==0.5.2
pytest-watch==4.2.0
pytest-xdist==1.18.1
python-dateutil==2.8.0
python-snappy==0.5.4
pytz==2019.3
PyYAML==5.1.2
readme-renderer==24.0
requests==2.22.0
requests-toolbelt==0.9.1
rlp==1.1.0
rpcudp==3.0.0
ruamel.yaml==0.15.98
six==1.12.0
sniffio==1.1.0
snowballstemmer==2.0.0
sortedcontainers==2.1.0
Sphinx==1.7.9
sphinx-rtd-theme==0.4.3
sphinxcontrib-asyncio==0.2.0
sphinxcontrib-websupport==1.1.2
SQLAlchemy==1.3.10
sqlalchemy-stubs==0.1
ssz==0.1.5
termcolor==1.1.0
text-unidecode==1.3
toml==0.10.0
toolz==0.10.0
towncrier==19.2.0
tox==2.7.0
tqdm==4.36.1
traitlets==4.3.3
trie==1.4.0
trinity==0.1.0a29
trio==0.11.0
trio-typing==0.2.0
twine==2.0.0
typed-ast==1.4.0
typing-extensions==3.7.4
u-msgpack-python==2.5.2
uPnPClient==0.0.8
urllib3==1.25.6
uvloop==0.11.2
varint==1.0.2
virtualenv==16.7.5
watchdog==0.9.0
wcwidth==0.1.7
web3==4.4.1
webencodings==0.5.1
websockets==5.0.1
yarl==1.3.0
zeroconf==0.23.0
What is wrong?
Local runs of Pytest fail. I've run a variety of commands, but will focus on plain
pytest
here.On issue is connected to a module
eth2spec
which is referenced twice in one script, but never appears in the project:Another is a problem with
Namespace
. @veox correctly identified that the issue is somewhere in theeth2
tests;--ignore=tests/eth2
circumvents these issues. I get 8 of them, but will put the output of one of them for reference:Lastly:
.pyc
files can't be removed, or more precisely, even if removed, will be autogenerated by Pytest when run.tox
is also failing, but the output is massive. If anyone wants to see it, I can post it.The text was updated successfully, but these errors were encountered: