[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Who is running QEMU automated tests, and when?

From: Thomas Huth
Subject: Re: [Qemu-devel] Who is running QEMU automated tests, and when?
Date: Wed, 9 May 2018 18:25:16 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0

On 09.05.2018 17:53, Alex Bennée wrote:
> Michael Clark <address@hidden> writes:
>> On Fri, Apr 27, 2018 at 2:04 AM, Peter Maydell <address@hidden>
>> wrote:
>>> On 26 April 2018 at 14:57, Eduardo Habkost <address@hidden> wrote:
>>>> Peter, do you have additional tests you run before merging a pull
>>>> request?  Additional test sets run before tagging a release?
>>> I run make && make check, on a variety of hosts, before merging
>>> any pull request. That's the only testing I do, and I don't
>>> do anything more before I do a tag.
>> This is what I do on riscv, however it is not yet automated:
> <snip>
>> We could bring a snapshot of riscv-tests into the QEMU tree however it
>> would be best if they retained the BSD license so we can share locally
>> added tests with upstream as upstream is adding tests periodically.
> Certainly it would be worth considering some smoke tests for
> tests/tcg/riscv that at least verify the basics CPU features work as
> expected.

 Hi Michael,

has one of the riscv machine an UART that can be programmed with some
few lines of assembler? In that case we could extend
tests/boot-serial-test.c to also check riscv. That's just a very, very
simple test, but it's better than nothing and indeed helped to find a
couple of bugs in the past already.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]