mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: RFC: Gitlab CI for barebox
Date: Tue, 8 Feb 2022 19:16:58 +0300	[thread overview]
Message-ID: <20220208191658.9dbe219f58321367a27bc8a1@gmail.com> (raw)
In-Reply-To: <20220205171233.ec081c7d777a7d267c26fdf5@gmail.com>

On Sat, 5 Feb 2022 17:12:33 +0300
Antony Pavlov <antonynpavlov@gmail.com> wrote:

> On Mon, 31 Jan 2022 11:39:45 +0100
> Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:
> 
> Hello Ahmad!
> 
> > On 30.01.22 13:00, Antony Pavlov wrote:
> > > Hi!
> > > 
> > > I have made simple Gitlab CI for barebox.
> > 
> > Nice.
> > 
> > > Gitlab CI runner setup instruction and
> > > the source for Debian 11 docker image can be found at:
> > > 
> > >   https://gitlab.com/frantony/barebox-gitlab-ci-runner
> > 
> > I had tried something similar, but with Github actions
> > 
> > https://github.com/a3f/barebox/actions/runs/740206381
> > 
> > I didn't have the time to pursue this further. I am fine
> > with Gitlab as well.
> > 
> > > 
> > > Sample gitlab-ci.yaml config file:
> > > 
> > >   https://gitlab.com/frantony/barebox/-/commit/b1ed597d8e67c8f76f4f98cd1c6605b936cf2471
> > 
> > Here's how it looks for Github actions with emulate.pl:
> > 
> > https://github.com/a3f/barebox/blob/emulate.pl/.github/workflows/build-configs.yaml
> 
> I have just update gitlab runner, please see https://gitlab.com/frantony/barebox-gitlab-ci-runner/-/commit/f90c3932f1e90f900c4d4304c6a54898a5ee0e1e
> 
> As a result runner can build barebox for openrisc architecture and run emulate.pl, see
> https://gitlab.com/frantony/barebox/-/pipelines/464224894
> 
> There is a problem with emulate.pl for MIPS (see https://gitlab.com/frantony/barebox/-/jobs/2058215656).
> 
> log/mips/console_main artifact contains the fragment:
> 
> ---- begin ----
> Hit any to stop autoboot:    3
> barebox@qemu malta:/ echo "YGIS""XTJCSB"
> YGISXTJCSB
> barebox@qemu malta:/ echo -o /cmd 'cat /env/data/config'; echo "EOVL""SAWCFS"; sh /cmd; echo "EOVL""SAWCFS" $?;
> EOVLSAWCFS
> could not open /env/data/config: No such file or directory
> EOVLSAWCFS 1
> barebox@qemu malta:/ echo -o /cmd selftest; echo "BOCZ""OJHGFV"; sh /cmd; echo "BOCZ""OJHGFV" $?;
> BOCZOJHGFV
> printf: all 116 tests passed
> progress_notifier: all 12 tests passed
> BOCZOJHGFV 0
> barebox@qemu malta:/
> ---- end ----
> 
> there is a problem: "could not open /env/data/config: No such file or directory"

The same problem with ARM architecture.
It looks like CONFIG_DEFAULT_ENVIRONMENT_GENERIC_NEW_IKCONFIG=y is set only in RISC-V virt{32/64}_defconfig.

-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


  reply	other threads:[~2022-02-08 16:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-30 12:00 Antony Pavlov
2022-01-31 10:39 ` Ahmad Fatoum
2022-01-31 11:12   ` Sascha Hauer
2022-02-05 14:12   ` Antony Pavlov
2022-02-08 16:16     ` Antony Pavlov [this message]
2022-02-08 18:30       ` Ahmad Fatoum
2022-02-08 18:33     ` Ahmad Fatoum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220208191658.9dbe219f58321367a27bc8a1@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox