[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PULL 0/9] Fourth RISC-V PR for QEMU 8.0
From: |
Thomas Huth |
Subject: |
Re: [PULL 0/9] Fourth RISC-V PR for QEMU 8.0 |
Date: |
Fri, 24 Feb 2023 07:56:41 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0 |
Hi!
On 23/02/2023 23.49, Palmer Dabbelt wrote:
On Wed, 22 Feb 2023 07:56:10 PST (-0800), Palmer Dabbelt wrote:
On Tue, 21 Feb 2023 08:43:47 PST (-0800), Peter Maydell wrote:
...
This seems to have caused CI to decide it needs to rerun the
'docker-opensbi' job, which doesn't work:
https://gitlab.com/qemu-project/qemu/-/jobs/3808319659
I don't understand what exactly is going on here -- Alex,
Bin, any ideas?
Why do we build the firmware in CI if we have checked in
binaries in pc-bios?
Should .gitlab-ci.d/opensbi/Dockerfile really still be
starting with Ubuntu 18.04 ? That is already older than our
set of supported platforms, and falls out of support from
Ubuntu in a couple of months.
I just sent along a patch
<20230222154938.9201-1-palmer@rivosinc.com/">https://lore.kernel.org/r/20230222154938.9201-1-palmer@rivosinc.com/>.
I have no idea how to test it in the CI, though...
1) Fork the qemu repository in gitlab to your account
2) Add a remote to your repo on your PC to point to the
forked gitlab repo (git remote add ...)
3) Read docs/devel/ci-jobs.rst.inc - you basically want
these two things:
git config --local alias.push-ci "push -o ci.variable=QEMU_CI=1"
git config --local alias.push-ci-now "push -o ci.variable=QEMU_CI=2"
4) If you now do a "git push-ci ..." to your forked repo,
you should be able to see the CI pipelines there
Nobody's replied, so I'm inclined to just drop the OpenSBI bump and re-send
the PR. At least that way we can avoid getting blocked on the CI issues.
There's some more in flight so there'll probably be a 5th round before the
freeze either way, at least this way the stuff that works can avoid getting
blocked.
Please note that pull requests are currently not processed
anyway ('til March 1st), see:
CAFEAcA83u_ENxDj3GJKa-xv6eLJGJPr_9FRDKAqm3qACyhrTgg@mail.gmail.com/">https://lore.kernel.org/qemu-devel/CAFEAcA83u_ENxDj3GJKa-xv6eLJGJPr_9FRDKAqm3qACyhrTgg@mail.gmail.com/
Thomas
- [PULL 3/9] hw/riscv/boot.c: make riscv_load_initrd() static, (continued)
- [PULL 3/9] hw/riscv/boot.c: make riscv_load_initrd() static, Palmer Dabbelt, 2023/02/17
- [PULL 5/9] target/riscv: Remove privileged spec version restriction for RVV, Palmer Dabbelt, 2023/02/17
- [PULL 6/9] MAINTAINERS: Add some RISC-V reviewers, Palmer Dabbelt, 2023/02/17
- [PULL 7/9] target/riscv: Smepmp: Skip applying default rules when address matches, Palmer Dabbelt, 2023/02/17
- [PULL 8/9] target/riscv: avoid env_archcpu() in cpu_get_tb_cpu_state(), Palmer Dabbelt, 2023/02/17
- [PULL 4/9] roms/opensbi: Upgrade from v1.1 to v1.2, Palmer Dabbelt, 2023/02/17
- [PULL 9/9] target/riscv: Fix vslide1up.vf and vslide1down.vf, Palmer Dabbelt, 2023/02/17
- Re: [PULL 0/9] Fourth RISC-V PR for QEMU 8.0, Peter Maydell, 2023/02/21