Describe the bug
In the process of packaging OpenRAM for GNU Guix I've been unable to run the unit tests as I would expect such: small-ish tests that check the software integrity after building it.
In OpenRAM there are some tests that seem to be defunct (compiler/tests/00_code_format_check_test.py which checks whether the year is set correctly in the copyright header), most others seem to depend on the presence of PDKs. Maybe I am missing something, but I'd rather dub the former a "source quality test" and the latter "end-to-end (e2e) tests".
Can you confirm unit tests don't successfully run currently or am I doing it wrong?
Version
1.2.49 (dev) commit f2db9fe
To Reproduce
Try to build it with the Guix package definition as proposed in this Pull Request (make sure to enable #:tests?)
Expected behavior
I'd expect unit tests to test the build of the software in its parts (units), hinting hackers/contributors and packagers alike towards issues (and regressions) in the build process.
Logs
If applicable, add logs or output to help explain your problem.
Additional context
Add any other context about the problem here.
ddcchmmqf4hjk9qh4msmdq0k0in13c-openram-1.2.49-0.f2db9fe.drv.gz
Describe the bug
In the process of packaging OpenRAM for GNU Guix I've been unable to run the unit tests as I would expect such: small-ish tests that check the software integrity after building it.
In OpenRAM there are some tests that seem to be defunct (
compiler/tests/00_code_format_check_test.pywhich checks whether the year is set correctly in the copyright header), most others seem to depend on the presence of PDKs. Maybe I am missing something, but I'd rather dub the former a "source quality test" and the latter "end-to-end (e2e) tests".Can you confirm unit tests don't successfully run currently or am I doing it wrong?
Version
1.2.49 (dev) commit f2db9fe
To Reproduce
Try to build it with the Guix package definition as proposed in this Pull Request (make sure to enable
#:tests?)Expected behavior
I'd expect unit tests to test the build of the software in its parts (units), hinting hackers/contributors and packagers alike towards issues (and regressions) in the build process.
Logs
If applicable, add logs or output to help explain your problem.
Additional context
Add any other context about the problem here.
ddcchmmqf4hjk9qh4msmdq0k0in13c-openram-1.2.49-0.f2db9fe.drv.gz