Vote +1, we have same requirements. Either LAVA could support different health check for different chip versions, or take one step back, just can disable health check on old version device, enable health on newest version only. Currently to avoid too many variants, we disable all healthy check for chipV1, chipV2, chipV3 etc.
------------------------------------------------------------------
Sender:lava-users-request <lava-users-request@lists.lavasoftware.org>
Sent At:2023 May 13 (Sat.) 08:00
Recipient:lava-users <lava-users@lists.lavasoftware.org>
Subject:Lava-users Digest, Vol 56, Issue 4
Send Lava-users mailing list submissions to
lava-users@lists.lavasoftware.org
To subscribe or unsubscribe via email, send a message with subject or
body 'help' to
lava-users-request@lists.lavasoftware.org
You can reach the person managing the list at
lava-users-owner@lists.lavasoftware.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Lava-users digest..."
Today's Topics:
1. Design decision help reagrding device-types and health-check
(gemad@outlook.com)
----------------------------------------------------------------------
Message: 1
Date: Fri, 12 May 2023 14:31:22 -0000
From: gemad@outlook.com
Subject: [Lava-users] Design decision help reagrding device-types and
health-check
To: lava-users@lists.lavasoftware.org
Message-ID:
<168390188210.1209.11677411661920883493@op-lists.linaro.org>
Content-Type: text/plain; charset="utf-8"
Hello,
I have 2 versions of a device which are identical in terms of the deploy and boot and DUT control command,
but they need different images to boot, I differentiate between them with tags,
how can I have the same health-check job running on both of them, but use different images ?
or shall I create 2 device-types for them ? ( doesn't sound like a clean solution )
Thanks
------------------------------
Subject: Digest Footer
_______________________________________________
Lava-users mailing list -- lava-users@lists.lavasoftware.org
To unsubscribe send an email to lava-users-leave@lists.lavasoftware.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
------------------------------
End of Lava-users Digest, Vol 56, Issue 4
*****************************************