Noel Maersk

I think you might've submitted this to the wrong repo.

@Kalroth you might like https://github.com/veox/sgminer/commit/f2f2bcedc73fef6338d501788ca238a83136e377 for easier versioning in bugreports. It is not perfect, but gets the job done.

Heads up! PR #1579 pulls in tests that routinely consume 3 GiB of RAM when exec'd in a single process, or ~ 8 GiB at peak when allowed to run...

(Unrelated to the above.) Note that there are other tests that aren't run, which are _not_ in `SLOWEST_TESTS`: https://github.com/ethereum/py-evm/blob/7e3b313dbb485fe16729cc40b442310afd750dc2/tests/json-fixtures/test_blockchain.py#L131-L148 Perhaps the function can be reworked to `skip`/`xfail` unsupported/incorrect, _then_ check...

Possibly combine with issue #1594?..

IMO this shouldn't go ahead until https://github.com/ethereum/trinity/issues/1478 is fixed... The underlying issue is in `py-evm` - no issue in this repo yet, can't formulate it concisely, [other than](https://github.com/ethereum/trinity/issues/1478#issuecomment-579715506): > Seems...

> Note: If content-type isn't application/json, text, or html, the binary report will be streamed back. If it is one of those types you can expect an error in the...

Meanwhile, perhaps you could try the following workaround, specifically so you can move on: ``` python # Trying to retrieve the report: response is binary if successful from json import...

The solution is wholly unacceptable to me. It writes to file on-disk as a side-effect, returns a plain string instead of a JSON-derived `dict`, and singles out `RetrieveExport`. If that...

@Exodus4400 Have you tried the workaround suggested in https://github.com/veox/python3-krakenex/issues/114#issuecomment-512778377?