From: Ilya Leoshkevich <iii@linux.ibm.com>
To: "Thomas Huth" <thuth@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: Re: [PULL 0/5] tcg patch queue
Date: Fri, 20 Jan 2023 11:53:12 +0100 [thread overview]
Message-ID: <fd1b116ac19feaaebbf82f8e41a24883af81f851.camel@linux.ibm.com> (raw)
In-Reply-To: <2c1eb92b-91f8-34d5-c5f7-a56a41ec807b@redhat.com>
On Fri, 2023-01-20 at 10:41 +0100, Thomas Huth wrote:
> On 16/01/2023 23.36, Richard Henderson wrote:
> > The following changes since commit
> > fb7e7990342e59cf67dbd895c1a1e3fb1741df7a:
> >
> > tests/qtest/qom-test: Do not print tested properties by default
> > (2023-01-16 15:00:57 +0000)
> >
> > are available in the Git repository at:
> >
> > https://gitlab.com/rth7680/qemu.git tags/pull-tcg-20230116
> >
> > for you to fetch changes up to
> > 61710a7e23a63546da0071ea32adb96476fa5d07:
> >
> > accel/tcg: Split out cpu_exec_{setjmp,loop} (2023-01-16 10:14:12
> > -1000)
> >
> > ----------------------------------------------------------------
> > - Reorg cpu_tb_exec around setjmp.
> > - Use __attribute__((target)) for buffer_is_zero.
> > - Add perfmap and jitdump for perf support.
> >
> > ----------------------------------------------------------------
> > Ilya Leoshkevich (3):
> > linux-user: Clean up when exiting due to a signal
> > accel/tcg: Add debuginfo support
> > tcg: add perfmap and jitdump
> >
> > Richard Henderson (2):
> > util/bufferiszero: Use __attribute__((target)) for
> > avx2/avx512
> > accel/tcg: Split out cpu_exec_{setjmp,loop}
>
> Hi Richard, hi Ilya,
>
> with the recent QEMU master branch (commit 701ed34), I'm now seeing
> failures
> in Travis:
>
> https://app.travis-ci.com/github/huth/qemu/jobs/593786529#L14411
>
> Everything was still fine a couple of days ago (commit fb7e799):
>
> https://app.travis-ci.com/github/huth/qemu/builds/259755664
>
> ... so it seems this is likely related to this pull request. Could
> you
> please have a look?
>
> Thanks,
> Thomas
>
I would expect this to be (temporarily) fixed by [1], but we probably
don't set GITLAB_CI in Travis. Would it make sense to set it? It looks
as if this variable is currently used only to skip certain tests.
If not, then maybe split it into QEMU_CI, GITLAB_CI and TRAVIS_CI?
https://lists.gnu.org/archive/html/qemu-devel/2023-01/msg04438.html
next prev parent reply other threads:[~2023-01-20 10:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 22:36 [PULL 0/5] tcg patch queue Richard Henderson
2023-01-16 22:36 ` [PULL 1/5] linux-user: Clean up when exiting due to a signal Richard Henderson
2023-01-16 22:36 ` [PULL 2/5] accel/tcg: Add debuginfo support Richard Henderson
2023-01-16 22:36 ` [PULL 3/5] tcg: add perfmap and jitdump Richard Henderson
2023-06-02 17:21 ` Peter Maydell
2023-06-03 20:35 ` Ilya Leoshkevich
2023-06-29 11:31 ` Philippe Mathieu-Daudé
2023-06-29 12:59 ` Richard Henderson
2023-06-30 12:39 ` Ilya Leoshkevich
2023-06-30 13:24 ` Richard Henderson
2023-12-07 9:51 ` Philippe Mathieu-Daudé
2025-05-19 15:07 ` Peter Maydell
2023-01-16 22:36 ` [PULL 4/5] util/bufferiszero: Use __attribute__((target)) for avx2/avx512 Richard Henderson
2023-01-16 22:36 ` [PULL 5/5] accel/tcg: Split out cpu_exec_{setjmp,loop} Richard Henderson
2023-01-17 15:47 ` [PULL 0/5] tcg patch queue Peter Maydell
2023-01-20 9:41 ` Thomas Huth
2023-01-20 10:50 ` Alex Bennée
2023-01-20 10:53 ` Ilya Leoshkevich [this message]
2023-01-20 12:51 ` Thomas Huth
2023-01-20 16:49 ` Alex Bennée
2023-01-21 6:07 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2024-05-23 16:15 Richard Henderson
2024-05-24 5:06 ` Richard Henderson
2023-01-16 22:36 Richard Henderson
2021-05-01 18:51 Richard Henderson
2021-05-01 19:27 ` no-reply
2021-05-02 13:32 ` Peter Maydell
2020-09-03 21:40 Richard Henderson
2020-09-06 13:07 ` Peter Maydell
2020-03-17 19:00 Richard Henderson
2020-03-17 23:34 ` no-reply
2020-03-19 10:17 ` Peter Maydell
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=fd1b116ac19feaaebbf82f8e41a24883af81f851.camel@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).