| Las[m] | lkcl: Do you make use of https://gitlab.lip6.fr/vlsi-eda/alliance too? | 10:56 |
|---|---|---|
| lkcl | Las[m], yes, it's one of the dependencies. you can see in the chroot script | 11:06 |
| lkcl | https://git.libre-soc.org/?p=dev-env-setup.git;a=blob;f=coriolis2-chroot;h=a19ef53f29965383026dd843247038f9ef5fd2c7;hb=63eab39255b833c09dd764d37b7e2570a057755d#l129 | 11:06 |
| lkcl | and here https://libre-soc.org/HDL_workflow/coriolis2/ | 11:07 |
| Las[m] | just noticed that... thanks | 11:07 |
| lkcl | the tools there are slowly being replaced however that is taking time, so it's still a dependency | 11:07 |
| lkcl | mikolajw: i'll need an email address... i think i have one somewhere | 11:08 |
| lkcl | mikolajw: you already have one | 11:09 |
| Las[m] | lkcl: Is there a subset of the binaries in Alliance that you don't need? | 11:11 |
| lkcl | Las[m], no, it doesn't work that way. everything is needed because it's a complete process, start to finish | 11:12 |
| lkcl | VLSI development is a multi-phase process. each tool performs a specific phase | 11:13 |
| Las[m] | lkcl: So every folder in https://gitlab.lip6.fr/vlsi-eda/alliance/-/tree/master/alliance/src is needed? | 11:14 |
| lkcl | yes, every folder and every tool is needed. | 11:20 |
| lkcl | there are no shortcuts possible here. | 11:21 |
| lkcl | sorry :) | 11:21 |
| Las[m] | Well, I'll try to get it running | 11:23 |
| lkcl | alliance is packaged for debian, already, so should be quite straightforward | 11:25 |
| lkcl | the only pain is that it's set up as relative (homedir) style install, but there shouuuld be an override for INSTALL_PREFIX | 11:26 |
| *** lx0 is now known as lxo | 16:19 | |
| ghostmansd | lkcl: iirc you mentioned bug in srad? | 20:10 |
| ghostmansd | Hm, I've re-checked the code. Apart of off-by-one bug, which you already spotted, the code should be fine... | 20:31 |
| ghostmansd-pc | how much does it take to execute soc/src/soc/simple/test/test_issuer.py? it's in _simple_ directory, Carl! | 20:40 |
| ghostmansd | [sigh] all this time I waited is to simply find out that SVP64State has no attribute spr. It seems I forgot to update the repo. | 20:44 |
| ghostmansd-pc | after the update: | 20:49 |
| ghostmansd-pc | File "/home/ghostmansd/src/nmutil/src/nmutil/nmoperator.py", line 148, in eq | 20:50 |
| ghostmansd-pc | rres = ao.eq(ai) | 20:50 |
| ghostmansd-pc | AttributeError: 'NoneType' object has no attribute 'eq | 20:50 |
| ghostmansd-pc | it seems I'll never be able to launch these tests from soc successfully | 20:50 |
| lkcl | ghostmansd, ehn? | 21:14 |
| lkcl | 1 se | 21:14 |
| lkcl | c | 21:14 |
| lkcl | python3 simple/test/test_issuer.py nosvp64 >& /tmp/f | 21:14 |
| lkcl | nmutil commit: | 21:15 |
| lkcl | commit efda080db6978d249a23003bec734f1cc07de329 (HEAD -> master, origin/master, origin/HEAD) | 21:16 |
| lkcl | Author: Luke Kenneth Casson Leighton <lkcl@lkcl.net> | 21:16 |
| lkcl | Date: Tue Aug 24 12:52:12 2021 +0100 | 21:16 |
| lkcl | likewise replace data_o with o_data and data_i with i_data | 21:16 |
| lkcl | soc commit: | 21:16 |
| lkcl | commit 09ef5133b667ac71a3f34a3f35144743217f7acc (HEAD -> master) | 21:16 |
| lkcl | Author: Luke Kenneth Casson Leighton <lkcl@lkcl.net> | 21:16 |
| lkcl | Date: Tue Aug 31 21:27:08 2021 +0100 | 21:16 |
| lkcl | anooother valid_o to convert to o_valid | 21:16 |
| ghostmansd | I launched it w/o options | 21:19 |
| ghostmansd | Maybe that's the problem | 21:19 |
| lkcl | the venv you use with python3 -m venv ~/.env, right? | 21:20 |
| ghostmansd | What should I do in order to run tests on soc? What are the repos to be updated? Only soc and openpower-isa, or more? | 21:20 |
| lkcl | everything | 21:20 |
| ghostmansd | Nope, I ran it on my schroot directly | 21:21 |
| ghostmansd | w/o venv | 21:21 |
| lkcl | ok | 21:21 |
| lkcl | ah with setup.py develop? | 21:21 |
| ghostmansd | Do we have the whole process documented? Re-installing the whole HDL workflow is, well, not the best option. | 21:21 |
| ghostmansd | Nope, simply python3 path-to-test | 21:22 |
| lkcl | yeah you can't run it that way. | 21:22 |
| lkcl | it has to be venv'd or system-wide install with setup.py develop | 21:22 |
| lkcl | there's a /home/ghostmansd/.env directory | 21:23 |
| ghostmansd | Ok, what's the way to run? Is it documented? I recall there were some hints on setup.py in HDL, but IIRC it's not about running tests... | 21:23 |
| lkcl | ghostmansd@75-224-155-23:~/src/soc$ python3 setup.py develop | 21:23 |
| lkcl | Traceback (most recent call last): | 21:23 |
| lkcl | File "setup.py", line 1, in <module> | 21:23 |
| lkcl | from setuptools import setup, find_packages | 21:23 |
| lkcl | ModuleNotFoundError: No module named 'setuptools' | 21:23 |
| lkcl | the instructions are: | 21:23 |
| lkcl | run the dev-env-setup script | 21:23 |
| lkcl | if the dev-env-setup script fails, that's NOT your problem, that's a bug to get fixed | 21:24 |
| ghostmansd | You're checking on Talos? | 21:24 |
| lkcl | yes | 21:24 |
| lkcl | ghostmansd@75-224-155-23:~/src/soc$ python3 setup.py develop | 21:24 |
| lkcl | Traceback (most recent call last): | 21:24 |
| lkcl | File "setup.py", line 1, in <module> | 21:24 |
| lkcl | from setuptools import setup, find_packages | 21:24 |
| lkcl | ModuleNotFoundError: No module named 'setuptools' | 21:24 |
| lkcl | ok so it looks like you've never run the setup.py | 21:24 |
| lkcl | which explains why it can never work | 21:24 |
| ghostmansd | Nope, never on talos | 21:24 |
| ghostmansd | But I posted results not from taloz | 21:25 |
| ghostmansd | *talos | 21:25 |
| lkcl | ahh ok | 21:25 |
| ghostmansd | The results I posted are from Debian VM | 21:25 |
| ghostmansd | Though w/o venv | 21:25 |
| lkcl | ok, then you run the dev-env-setup w/o venv | 21:25 |
| ghostmansd | Anyway, I'd rather prefer Talos | 21:25 |
| lkcl | and there should be absolutely no problem whatsoever | 21:25 |
| lkcl | as long as you have *only* run the dev-env-setup script and not attempted anything else | 21:26 |
| ghostmansd | lkcl: how about we finally complete establishing environment on Talos, since it's obviously better performance-wise than my laptop? | 21:27 |
| ghostmansd | So far I used only some virtualenv-related script on Talos, and I have all repos I think I should have | 21:28 |
| ghostmansd | Should I also run dev-env-setup on Talos? | 21:28 |
| ghostmansd | Anything else? I suspect the HDL workflow does not exactly fit Talos. | 21:28 |
| lkcl | no absolutely not | 21:30 |
| lkcl | it is currently a debian/testing system and i am trying to sort it out | 21:30 |
| lkcl | debian/testing was the only way that the system could be installed (at all) due to it being a remote-managed server | 21:30 |
| lkcl | fricking nuisance | 21:31 |
| lkcl | probably going to have to tolerate python 3.9 | 21:31 |
| lkcl | ok making progress | 21:37 |
| lkcl | i'm going through it manually for you but using python3 setup.py develop --user | 21:38 |
| lkcl | which installs python packages into ~/.local/ | 21:38 |
| lkcl | it's 1/2 way through pywriter | 21:39 |
| lkcl | ok that's done | 21:40 |
| lkcl | soc install next | 21:40 |
| lkcl | oh ha ha very funny | 21:42 |
| lkcl | no powerpc64le-linux-gnu-as | 21:42 |
| lkcl | because, duh, this is native | 21:42 |
| lkcl | i thought that would happen | 21:43 |
| lkcl | errrrmmm... ermermerm... how to detect that... | 21:43 |
| lkcl | >>> import platform | 21:44 |
| lkcl | >>> platform.machine() | 21:44 |
| lkcl | 'ppc64le' | 21:44 |
| lkcl | that'lldo | 21:44 |
| lkcl | ghostmansd, okaaay that's running | 21:49 |
| lkcl | on the TALOS-II workstation, under your homedir | 21:49 |
| lkcl | test_issuer.py nosvp64 | 21:50 |
| * lkcl trying test_caller.py in openpower-isa | 21:50 | |
| ghostmansd | If this works, that'd be great, since it closes two questions: 1) always disturbing you with testing; 2) fixing potential issues on-the-fly | 21:52 |
| lkcl | no errors in test_caller.py | 21:53 |
| lkcl | and i leave you to inspect the output of test_issuer.py, it outputted to /tmp/x | 21:53 |
| lkcl | test_caller.py i outputted to /tmp/y | 21:53 |
| * lkcl tired. rest | 21:54 | |
| ghostmansd | Anyway, when the environment is ready, I must know in the future what to update and how. Should I go over all repositories in src with `git pull origin master --rebase` and `git submodule update --recursive`? Should I also re-build pia? Should I go through the whole HDL? | 21:55 |
| ghostmansd | That's not urgent, but really desired eventually. I have no idea how soc works, I'm new to it. | 21:55 |
| ghostmansd | openpower-isa was a good one to start, since it's somewhat self-contained. But I don't have a picture of the overall project architecture. | 21:56 |
| ghostmansd | Thank you for help! I hope I'll be able to check these tomorrow. But most likely I will check on weekends, since I'm overwhelmed by everyday work and family needs (the latter are at least nice and pleasant, though). | 21:57 |
| programmerjake | you can rebuild pia if you like, but it's not necessary unless your moving to a different python environment | 22:07 |
| lkcl | ghostmansd, it's good. yes basically git pull (at least) and, as you've already been doing, if that was on openpower-isa you need to identify if .mdwn files were modified and re-run the appropriate compiler | 22:55 |
| lkcl | (pywriter, pyfnwriter) | 22:56 |
| lkcl | you've already been doing that so know how it's done | 22:56 |
| lkcl | (and how to take relevant shortcuts) | 22:56 |
| lkcl | there's no need to re-run python3 setup.py install | 22:56 |
| lkcl | because we don't *use* python3 setup.py install | 22:56 |
| lkcl | we use python3 setup.py *develop* | 22:56 |
| lkcl | precisely because it does *NOT* take a copy and point you at the copy | 22:57 |
| lkcl | programmerjake, sigh, had to use python3.9 on talos1. ngggh | 23:00 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!