All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Berger <stefanb@linux.ibm.com>
To: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>,
	The development of GNU GRUB <grub-devel@gnu.org>
Cc: Gary Lin <glin@suse.com>, Daniel Kiper <daniel.kiper@oracle.com>,
	Michael Chang <mchang@suse.com>,
	patrick.colp@oracle.com, jejb@linux.ibm.com,
	Glenn Washburn <development@efficientek.com>
Subject: Re: [PATCH v4 09/12] tests/tpm2_key_protector_test: Reset 'ret' on fail
Date: Mon, 24 Mar 2025 10:35:13 -0400	[thread overview]
Message-ID: <69b97baa-3422-4198-a65d-2b8a7245c028@linux.ibm.com> (raw)
In-Reply-To: <CAEaD8JN6U_Zk2XoLWw4ppFnwyoKU+jrXm7oekzvpByTddGbE0w@mail.gmail.com>



On 3/24/25 10:29 AM, Vladimir 'phcoder' Serbinenko wrote:
> Is there a risk here of missing the failures? It's common that no one 
> looks at the output unless it causes a failed build on some CI/CD Le 

Good point. Maybe the test script should return '1' when a single error 
occurred but run all tests nevertheless?

> ven. 21 mars 2025, 11: 01, Gary Lin via Grub-devel <grub-devel@ gnu.  
> org> a écrit : Reset 'ret'
> 
> Is there a risk here of missing the failures? It's common that no one 
> looks at the output unless it causes a failed build on some CI/CD
> 
> Le ven. 21 mars 2025, 11:01, Gary Lin via Grub-devel <grub-devel@gnu.org 
> <mailto:grub-devel@gnu.org>> a écrit :
> 
>     Reset 'ret' to 0 when a test case fails so that the other test cases
>     could continue.
> 
>     Signed-off-by: Gary Lin <glin@suse.com <mailto:glin@suse.com>>
>     ---
>       tests/tpm2_key_protector_test.in <http://
>     tpm2_key_protector_test.in> | 2 ++
>       1 file changed, 2 insertions(+)
> 
>     diff --git a/tests/tpm2_key_protector_test.in <http://
>     tpm2_key_protector_test.in> b/tests/tpm2_key_protector_test.in
>     <http://tpm2_key_protector_test.in>
>     index 07477ba2a..0d1115e02 100644
>     --- a/tests/tpm2_key_protector_test.in <http://
>     tpm2_key_protector_test.in>
>     +++ b/tests/tpm2_key_protector_test.in <http://
>     tpm2_key_protector_test.in>
>     @@ -291,6 +291,7 @@ for i in "${!srktests[@]}"; do
>               echo "TPM2 [${srktests[$i]}]: PASS"
>           elif [ "${ret}" -eq 1 ]; then
>               echo "TPM2 [${srktests[$i]}]: FAIL"
>     +       ret=0
>           else
>              echo "Unexpected failure [${srktests[$i]}]" >&2
>              exit ${ret}
>     @@ -303,6 +304,7 @@ if [ "${ret}" -eq 0 ]; then
>           echo "TPM2 [NV Index]: PASS"
>       elif [ "${ret}" -eq 1 ]; then
>           echo "TPM2 [NV Index]: FAIL"
>     +    ret=0
>       else
>           echo "Unexpected failure [NV index]" >&2
>           exit ${ret}
>     -- 
>     2.43.0
> 
> 
>     _______________________________________________
>     Grub-devel mailing list
>     Grub-devel@gnu.org <mailto:Grub-devel@gnu.org>
>     https://lists.gnu.org/mailman/listinfo/grub-devel <https://
>     lists.gnu.org/mailman/listinfo/grub-devel>
> 


_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

  reply	other threads:[~2025-03-24 14:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21  7:58 [PATCH v4 00/12] TPM2 key protector follow-up patches Gary Lin via Grub-devel
2025-03-21  7:58 ` [PATCH v4 01/12] tpm2_key_protector: dump PCRs on policy fail Gary Lin via Grub-devel
2025-03-21  7:58 ` [PATCH v4 02/12] tpm2_key_protector: Add 'tpm2_dump_pcr' command Gary Lin via Grub-devel
2025-03-21  7:58 ` [PATCH v4 03/12] tss2: Fix the missing authCommand Gary Lin via Grub-devel
2025-03-21  7:59 ` [PATCH v4 04/12] tss2: Add TPM 2.0 NV index commands Gary Lin via Grub-devel
2025-03-21  7:59 ` [PATCH v4 05/12] tpm2_key_protector: Unseal key from a buffer Gary Lin via Grub-devel
2025-03-25 16:01   ` Daniel Kiper via Grub-devel
2025-03-26  7:54     ` Gary Lin via Grub-devel
2025-03-21  7:59 ` [PATCH v4 06/12] tpm2_key_protector: Support NV index handles Gary Lin via Grub-devel
2025-03-21  7:59 ` [PATCH v4 07/12] util/grub-protect: Support NV index mode Gary Lin via Grub-devel
2025-03-26 16:14   ` Daniel Kiper via Grub-devel
2025-03-21  7:59 ` [PATCH v4 08/12] tests/tpm2_key_protector_test: Simplify the NV index mode test Gary Lin via Grub-devel
2025-03-24 14:21   ` Stefan Berger
2025-03-26 16:16   ` Daniel Kiper via Grub-devel
2025-03-21  7:59 ` [PATCH v4 09/12] tests/tpm2_key_protector_test: Reset 'ret' on fail Gary Lin via Grub-devel
2025-03-24 13:48   ` Stefan Berger
2025-03-24 14:29   ` Vladimir 'phcoder' Serbinenko
2025-03-24 14:35     ` Stefan Berger [this message]
2025-03-25  7:18       ` Gary Lin via Grub-devel
2025-03-21  7:59 ` [PATCH v4 10/12] tests/tpm2_key_protector_test: Add more NV index mode tests Gary Lin via Grub-devel
2025-03-24 14:19   ` Stefan Berger
2025-03-21  7:59 ` [PATCH v4 11/12] docs: Update NV index mode of TPM2 key protector Gary Lin via Grub-devel
2025-03-21  7:59 ` [PATCH v4 12/12] INSTALL: Document the packages needed for TPM2 key protector tests Gary Lin via Grub-devel
2025-03-26 16:19   ` Daniel Kiper via Grub-devel

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=69b97baa-3422-4198-a65d-2b8a7245c028@linux.ibm.com \
    --to=stefanb@linux.ibm.com \
    --cc=daniel.kiper@oracle.com \
    --cc=development@efficientek.com \
    --cc=glin@suse.com \
    --cc=grub-devel@gnu.org \
    --cc=jejb@linux.ibm.com \
    --cc=mchang@suse.com \
    --cc=patrick.colp@oracle.com \
    --cc=phcoder@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.