Closed Kaucasus closed 2 years ago
@Kaucasus thanks for reporting this. Can I ask what python version are you using ? Also what version of riscof you are using (riscof --version should do the trick)
@pawks any thoughts ?
The Python version as reported by Python --version
is 3.6.0 (managed by pyenv), and riscof is RISC-V Architectural Test Framework., version 1.23.2
As far as I could trace it out, it seems to be an error due to using python 3.6.0
and Jinja 3.0.1
. Please try downgrading Jinja
to 3.0.0 using pip install jinja==3.0.0
or upgrade to python 3.6.x
.
Link to issue on Jinja repo - https://github.com/pallets/jinja/issues/1459
Note: If you are using pyenv
it is better to shift to one of the more recent stable versions of python like 3.7.x
or later.
I updated my python environment via pyenv to target 3.8.10. Installing riscof in that environment works as intended!
(well, technically because I run WSL the browser can't automatically open, but the report.html gets generated, and running with the --no-browser
flag exists cleanly).
Thank you very much for the quick and speedy resulotion!
@pawks since riscof is meant for python 3.6 maybe we should freeze Jinja at 3.0.0 in the requirements.txt ?
That would be a short term fix for sure. However, official support for python 3.6 ends in December 2021 and many problems may arise in future when other packages also start dropping support.
Tracking the issue in #43
When trying to follow the quickstart guide as in: https://riscof.readthedocs.io/en/stable/installation.html# the
riscof run
command at the very end fails.I've followed the installation step by step on a clean Ubuntu 20.04 LTS install in Windows Subsystem for Linux with the following directories and decisions made with every step succeeding:
~/.pyenv
and activated the shell~/riscof
~/riscv-sims/riscv-isa-sim
and ./configure install prefix path~/riscv-sims/spike
~/riscv-sims/sail-riscv
~/risctest/spike
, ran theriscof setup --dutname=spike
commandThen, finally running in the same directory
riscof run --config=config.ini --suite=riscv-arch-test/riscv-test-suite/ --env=riscv-arch-test/riscv-test-suite/env
fails with a Python AttributeError: 'Token' object has no attribute 'test'.It does not open up a HTML page with the test results, and just exits. Seemingly, the tool does simulate and collects the test signature for both the reference and the dut. The tool also seemingly runs perfect up to that point, and logs the info messages to the shell no problem. A full stacktrace can be found below:
If anybody has an idea how to solve this issue, or if you need more information about my file structure, do let me know!