Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: patchtest@automation.yoctoproject.org
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Patchtest results for [PATCH] docbook-xml-dtd4: correct license name
Date: Mon, 10 Mar 2025 15:29:09 +0800	[thread overview]
Message-ID: <64fe699d-a030-4777-82fa-faef18ca9c22@windriver.com> (raw)
In-Reply-To: <010101957ee9e7b8-265cb694-4d61-42b6-b160-8ba936e42232-000000@us-west-2.amazonses.com>

[-- Attachment #1: Type: text/plain, Size: 3898 bytes --]

On 3/10/25 15:16, patchtest@automation.yoctoproject.org wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> 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/docbook-xml-dtd4-correct-license-name.patch
>
> FAIL: test src uri left files: Patches not removed from tree. Remove them and amend the submitted mbox (test_metadata.TestMetadata.test_src_uri_left_files)

I am afraid it is a false alarm,

the local file 
meta/recipes-devtools/docbook-xml/docbook-xml-dtd4/LICENSE-OASIS was 
removed,

and rename meta/files/common-licenses/OASIS to 
meta/files/common-licenses/DocBook

But the review patch renamed 
meta/recipes-devtools/docbook-xml/docbook-xml-dtd4/LICENSE-OASIS to 
meta/files/common-licenses/DocBook

and remove meta/files/common-licenses/OASIS

rename from meta/recipes-devtools/docbook-xml/docbook-xml-dtd4/LICENSE-OASIS
rename to meta/files/common-licenses/DocBook
...
--- a/meta/files/common-licenses/OASIS
+++ /dev/null

//Hongxu

> PASS: pretest src uri left files (test_metadata.TestMetadata.pretest_src_uri_left_files)
> PASS: test CVE check ignore (test_metadata.TestMetadata.test_cve_check_ignore)
> 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 commit message user tags (test_mbox.TestMbox.test_commit_message_user_tags)
> PASS: test lic files chksum modified not mentioned (test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)
> 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 shortlog format (test_mbox.TestMbox.test_shortlog_format)
> PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length)
> PASS: test target mailing list (test_mbox.TestMbox.test_target_mailing_list)
>
> SKIP: pretest pylint: No python related patches, skipping test (test_python_pylint.PyLint.pretest_pylint)
> 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 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 pylint: No python related patches, skipping test (test_python_pylint.PyLint.test_pylint)
> SKIP: test series merge on head: Merge test is disabled for now (test_mbox.TestMbox.test_series_merge_on_head)
> SKIP: test summary presence: No added recipes, skipping test (test_metadata.TestMetadata.test_summary_presence)
>
> ---
>
> 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 athttps://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!


[-- Attachment #2: Type: text/html, Size: 7428 bytes --]

  reply	other threads:[~2025-03-10  7:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-10  7:12 [PATCH] docbook-xml-dtd4: correct license name Hongxu Jia
2025-03-10  7:16 ` Patchtest results for " patchtest
2025-03-10  7:29   ` Hongxu Jia [this message]
2025-03-17 12:43 ` [OE-core] " Ross Burton
2025-03-19  2:41   ` Hongxu Jia

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=64fe699d-a030-4777-82fa-faef18ca9c22@windriver.com \
    --to=hongxu.jia@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=patchtest@automation.yoctoproject.org \
    /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