From: Bui Quang Minh <minhquangbui99@gmail.com>
To: Thomas Huth <thuth@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Phil Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: CI "pages" job failing with incomprehensible error message from htags
Date: Mon, 8 Jan 2024 21:41:41 +0700 [thread overview]
Message-ID: <0fecbb98-9019-4a3a-a764-38e848b5b238@gmail.com> (raw)
In-Reply-To: <9f0615dc-c162-4ac6-9ead-7f9d28e5d318@redhat.com>
On 1/8/24 18:03, Thomas Huth wrote:
> On 05/01/2024 20.11, Peter Maydell wrote:
>> https://gitlab.com/qemu-project/qemu/-/jobs/5871592479
>>
>> failed with
>>
>> $ htags -anT --tree-view=filetree -m qemu_init -t "Welcome to the QEMU
>> sourcecode"
>> htags: Negative exec line limit = -371
>>
>> Does anybody have any idea what this is about ?
>
> In case you haven't spotted it yet:
>
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg1014394.html
>
> Is anybody already already creating a patch to clear CI_COMMIT_MESSAGE
> when invoking htags ?
That solution works fine on my CI, however, it is stated in Gitlab
documentation that overriding predefined variables is not recommended.
https://docs.gitlab.com/ee/ci/variables/predefined_variables.html
Avoid overriding predefined variables, as it can cause the pipeline to
behave unexpectedly.
Thanks,
Quang Minh.
next prev parent reply other threads:[~2024-01-08 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 19:11 CI "pages" job failing with incomprehensible error message from htags Peter Maydell
2024-01-08 11:03 ` Thomas Huth
2024-01-08 12:34 ` Peter Maydell
2024-01-08 12:57 ` Peter Maydell
2024-01-08 14:41 ` Bui Quang Minh [this message]
2024-01-08 15:10 ` 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=0fecbb98-9019-4a3a-a764-38e848b5b238@gmail.com \
--to=minhquangbui99@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@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).