haritzondo has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
haritz has joined #u-boot
haritz has quit [Changing host]
haritz has joined #u-boot
<Forty-Bot>
kallisti5: send a ping or something :)
guillaume_g has quit [Quit: Konversation terminated!]
eduardas has quit [Quit: Konversation terminated!]
frieder has quit [Remote host closed the connection]
tnovotny has quit [Quit: Leaving]
redbrain has joined #u-boot
fdanis is now known as fdanis_away
<mrnuke>
marex: heh. I tried
sakman has quit [Remote host closed the connection]
redbrain has quit [Ping timeout: 252 seconds]
sakman has joined #u-boot
sakman has quit [Remote host closed the connection]
sakman has joined #u-boot
sakman has quit [Remote host closed the connection]
LokeshVutla has quit [Remote host closed the connection]
redbrain has joined #u-boot
<mrnuke>
If I wanted to run the same tests that giglab-CI does, but without access to gitlab, how would I do that from a shell?
<mrnuke>
I was able to get the docker container, as described in -- doc, but not sure how to start the actual build tests
<Harm>
The .gitlab-ci.yml file describes how the tests are run
<Harm>
You could push your u-boot code to gitlab.com and build from there
sakman has joined #u-boot
<marex>
mrnuke: you mean to run some very specific simple u-boot CI test ?
<marex>
mrnuke: without trying to decode how to do it from the .gitlab-ci.yaml file and without having to install all the bloated dead whale docker stuff ?
<marex>
mrnuke: I really dislike the overhead of that
<mrnuke>
I mean how to run the tests that Tartarus graciously found out the hard way are failing. I'm trying to prevent the problem of pushing a well intentioned series that fails CI miserably
<mrnuke>
marex: I don't mind running docker (assuming it's not some braindead long silly commandline). Lots od M$ software at work, so they already have machines that threw a lot of hardware at a software issue
<Tartarus>
mrnuke: doc/develop/ci_testing.rst
<Tartarus>
The readthedocs.io site doesn't update until next big release
<Tartarus>
in short, if you use github you can get azure to fire off and run for just the cost of a github account + fork
<mrnuke>
I was hoping there would be a way to do it locally. I have access to a decent machine that could test things much faster than the interwebs