From: "Mittal, Anuj" <anuj.mittal@intel.com>
To: "ticotimo@gmail.com" <ticotimo@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: Patchtest results for [OE-core][PATCH] patchtest: shorten test result outputs
Date: Wed, 1 Nov 2023 02:48:15 +0000 [thread overview]
Message-ID: <8c789be17c092ff433b7b4499388f957c32663ef.camel@intel.com> (raw)
In-Reply-To: <CANx9H-CCaTwnVc+KW+sAUJjMutNtNw-T0Rybpdw1kM7o+_qMzg@mail.gmail.com>
On Tue, 2023-10-31 at 19:33 -0700, Tim Orling wrote:
>
>
> On Tue, Oct 31, 2023 at 7:26 PM Anuj Mittal <anuj.mittal@intel.com>
> wrote:
> > On Tue, 2023-10-31 at 14:20 +0000, Trevor Gamblin wrote:
> > > Thank you for your submission. Patchtest identified one
> > > or more issues with the patch. Please see the log below for
> > > more information:
> > >
> > > ---
> > > Testing patch /home/patchtest/share/mboxes/patchtest-shorten-
> > > test-
> > > result-outputs.patch
> > >
> > > FAIL: test CVE presence in commit message: A CVE tag should be
> > > provided in the commit message with format: "CVE: CVE-YYYY-XXXX"
> > > (test_mbox.TestMbox.test_cve_presence_in_commit_message)
> >
> > Is this a requirement to have this in commit message in this
> > format? I
> > don't think this was being followed until now. A lot of patches
> > seem to
> > be failing this test as a result.
> >
>
>
> This was required when patchtest was running previously. It has been
> ignored for a while now, but that does not mean we should not enforce
> it. It should be documented as required.
>
> The tags allow for machines to parse the relevant info. Anything else
> is purely random and chaos.
The tag is already required to be present in the CVE patch itself which
is/can be parsed by scripts which actually I think is a better way of
detecting whether a CVE is patched rather than looking at commit
messages.
If having it in a specific format in commit message as well helps,
sure. It shouldn't take time to add it but we seem to be adding too
many rules ...
Thanks,
Anuj
>
> >
> > The wiki just mentions that CVE number should be in commit message.
> >
> > Thanks,
> >
> > Anuj
> >
> > >
> > > PASS: pretest pylint (test_python_pylint.PyLint.pretest_pylint)
> > > PASS: test Signed-off-by presence
> > > (test_mbox.TestMbox.test_signed_off_by_presence)
> > > PASS: test author valid (test_mbox.TestMbox.test_author_valid)
> > > PASS: test commit message presence
> > > (test_mbox.TestMbox.test_commit_message_presence)
> > > PASS: test max line length
> > > (test_metadata.TestMetadata.test_max_line_length)
> > > PASS: test mbox format (test_mbox.TestMbox.test_mbox_format)
> > > PASS: test non-AUH upgrade
> > > (test_mbox.TestMbox.test_non_auh_upgrade)
> > > PASS: test pylint (test_python_pylint.PyLint.test_pylint)
> > > PASS: test shortlog format
> > > (test_mbox.TestMbox.test_shortlog_format)
> > > PASS: test shortlog length
> > > (test_mbox.TestMbox.test_shortlog_length)
> > >
> > > SKIP: pretest lic files chksum modified not mentioned: No
> > > modified
> > > recipes, skipping pretest
> > > (test_metadata.TestMetadata.pretest_lic_files_chksum_modified_not
> > > _men
> > > tioned)
> > > SKIP: pretest src uri left files: No modified recipes, skipping
> > > pretest (test_metadata.TestMetadata.pretest_src_uri_left_files)
> > > SKIP: test CVE tag format: No new CVE patches introduced
> > > (test_patch.TestPatch.test_cve_tag_format)
> > > SKIP: test Signed-off-by presence: No new CVE patches introduced
> > > (test_patch.TestPatch.test_signed_off_by_presence)
> > > SKIP: test Upstream-Status presence: No new CVE patches
> > > introduced
> > > (test_patch.TestPatch.test_upstream_status_presence_format)
> > > SKIP: test bugzilla entry format: No bug ID found
> > > (test_mbox.TestMbox.test_bugzilla_entry_format)
> > > SKIP: test lic files chksum modified not mentioned: No modified
> > > recipes, skipping test
> > > (test_metadata.TestMetadata.test_lic_files_chksum_modified_not_me
> > > ntio
> > > ned)
> > > SKIP: test lic files chksum presence: No added recipes, skipping
> > > test
> > > (test_metadata.TestMetadata.test_lic_files_chksum_presence)
> > > SKIP: test license presence: No added recipes, skipping test
> > > (test_metadata.TestMetadata.test_license_presence)
> > > SKIP: test series merge on head: Merge test is disabled for now
> > > (test_mbox.TestMbox.test_series_merge_on_head)
> > > SKIP: test src uri left files: No modified recipes, skipping
> > > pretest
> > > (test_metadata.TestMetadata.test_src_uri_left_files)
> > > SKIP: test summary presence: No added recipes, skipping test
> > > (test_metadata.TestMetadata.test_summary_presence)
> > > SKIP: test target mailing list: Series merged, no reason to check
> > > other mailing lists (test_mbox.TestMbox.test_target_mailing_list)
> > >
> > > ---
> > >
> > > Please address the issues identified and
> > > submit a new revision of the patch, or alternatively, reply to
> > > this
> > > email with an explanation of why the patch should be accepted. If
> > > you
> > > believe these results are due to an error in patchtest, please
> > > submit
> > > a
> > > bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest'
> > > category
> > > under 'Yocto Project Subprojects'). For more information on
> > > specific
> > > failures, see: https://wiki.yoctoproject.org/wiki/Patchtest.
> > > Thank
> > > you!
> > >
> > >
> > >
> >
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#189893):
> > https://lists.openembedded.org/g/openembedded-core/message/189893
> > Mute This Topic: https://lists.openembedded.org/mt/102275009/924729
> > Group Owner: openembedded-core+owner@lists.openembedded.org
> > Unsubscribe:
> > https://lists.openembedded.org/g/openembedded-core/unsub
> > [ticotimo@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
next prev parent reply other threads:[~2023-11-01 2:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 14:20 Patchtest results for [OE-core][PATCH] patchtest: shorten test result outputs patchtest
2023-10-31 14:54 ` Michael Opdenacker
2023-10-31 15:06 ` Trevor Gamblin
2023-11-01 2:26 ` Mittal, Anuj
2023-11-01 2:33 ` Tim Orling
2023-11-01 2:48 ` Mittal, Anuj [this message]
2023-11-01 5:31 ` Marta Rybczynska
2023-11-01 13:48 ` Steve Sakoman
2023-11-01 14:00 ` Trevor Gamblin
[not found] ` <179368C4B8E65457.29356@lists.openembedded.org>
2023-11-01 6:27 ` Marta Rybczynska
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 17:18 patchtest
2023-11-01 17:48 patchtest
2023-11-01 17:47 patchtest
2023-10-30 15:20 patchtest
2023-10-30 13:41 patchtest
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=8c789be17c092ff433b7b4499388f957c32663ef.camel@intel.com \
--to=anuj.mittal@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ticotimo@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.