[Libre-soc-bugs] [Bug 1235] resolve openpower-isa repository screwups

[bugzilla-daemon at libre-soc.org]

https://bugs.libre-soc.org/show_bug.cgi?id=1235

--- Comment #4 from Jacob Lifshay <programmerjake at gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #3)
> i really don't want hard-coded dependence on a remote CI server
> especially one that i (personally) do not have any access to
> let alone knowledge of its setup and workings.

other than the access to the fpga, which openpower-isa doesn't use, it is a
bog-standard gitlab-runner install using docker. nothing special. the parts
that are special are the things that run git mirroring and the program that
asks the gitlab server for the build log when it's done, neither of which
affect how CI is run.
> 
> (remember: i did instruct you not to use latest-and-greatest,

I'm not. I'm using the version specified in the dev scripts.

I think you probably forgot to update to the latest version of the dev scripts,
since they specify the exact same version of pytest used in CI, which does work
with that option. the versions were changed a while ago shortly after they were
initially added to the dev scripts.

please add the option back in, it substantially improves CI performance iirc.

> if you can convert the CI environment to be one that uses
> *exclusively project standard development environment* and
> also allows anyone and i do mean anyone to install it as
> a stand-alone setup / VM, then we have a way forward to using
> CI.

CI runs in docker by gitlab-runner and is reproducible (unless I missed
something, this excludes that it uses the latest master version of the
libre-soc repos such as nmutil), all you need is to run it with any gitlab
installation.

you can also run it (will be much slower due to lack of build cache) without a
whole gitlab install by just installing the gitlab-runner and docker packages
and running (in the openpower-isa git repo):
gitlab-runner exec docker build

> (i.e. *any* laptop / server used by *any* developer should
>  have a devscript that they can personally run and trigger
>  unit tests - selectively - to produce results)

there isn't a script, since it's just installing the dev environment and then
running pytest.

-- 
You are receiving this mail because:
You are on the CC list for the bug.