Skip to content

backport: Add error handling for unsupported flavor options - #375

Open
pravalikagurram1 wants to merge 1 commit into
intel-gpu:kernel-backport/v6.17from
pravalikagurram1:backport_shell
Open

backport: Add error handling for unsupported flavor options#375
pravalikagurram1 wants to merge 1 commit into
intel-gpu:kernel-backport/v6.17from
pravalikagurram1:backport_shell

Conversation

@pravalikagurram1

Copy link
Copy Markdown

Add an else case to the flavor validation logic in apply_patches() to
handle invalid or unsupported flavor specifications. When a user
provides a flavor that is not in the supported list (base, features, oot),
the script now displays an error message with the list of supported options
and exits with error status code 1, instead of silently continuing."

Signed-off-by: Pravalika Gurram pravalika.gurram@intel.com

@ayazahma ayazahma left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there is no point to have two commits , they should merge togather
I think we should provide , also in case error , we should just print waring that un supporrted option and fall back to default

@ayazahma

Copy link
Copy Markdown
Contributor

Also This change is not critical, so I suggest completing functional implementier oot backport Change etc along with these Change

can I have pr for backport tool, to use oot option
pr for oot-backport to remove patch from oot-backport and use kernel backport patch

Add an else case to the flavor validation logic in apply_patches() to
handle invalid or unsupported flavor specifications. When a user
provides a flavor that is not in the supported list (base, features, oot),
the script now displays an error message with the list of supported options
and exits with error status code 1, instead of silently continuing."

Refactor: Use switch statement for flavor selection in apply_patches()
Convert nested if-elif-else logic to a switch/case statement for improved
readability. No functional changes - only refactoring for better code structure.

Signed-off-by: Pravalika Gurram <pravalika.gurram@intel.com>
@sys-i915-oscijenkins

Copy link
Copy Markdown

CI Bug Log - changes from xkb-6.17-267-19320f0c49ae77de8f6c80be66114cc4ec84aa5a_BAT -> xkb-pr-6.17-375-616-c50a59e95c6797ce6f7873e6319681048479bf7d_BAT

Summary

SUCCESS

No regressions found.

Participating hosts (9 -> 9)

No changes in participating hosts

Known issues

Here are the changes found in xkb-pr-6.17-375-616-c50a59e95c6797ce6f7873e6319681048479bf7d_BAT that come from known issues:

IGT changes

Issues hit

Possible fixes

Build changes

  • IGT: igt-xkb-116-b37ea8adf -> igt-xkb-117-4870154c2
  • Linux: xkb-6.17-267-19320f0c49ae77de8f6c80be66114cc4ec84aa5a -> xkb-pr-6.17-375-616-c50a59e95c6797ce6f7873e6319681048479bf7d

igt-xkb-116-b37ea8adf: b37ea8adf
igt-xkb-117-4870154c2: 4870154c2
xkb-6.17-267-19320f0c49ae77de8f6c80be66114cc4ec84aa5a: 19320f0
xkb-pr-6.17-375-616-c50a59e95c6797ce6f7873e6319681048479bf7d: c50a59e

@sys-i915-oscijenkins

Copy link
Copy Markdown

CI Bug Log - changes from xkb-6.17-267-19320f0c49ae77de8f6c80be66114cc4ec84aa5a_BAT -> xkb-pr-6.17-375-618-58f684aba8289f92b467ac42f11ea6598203b62f_BAT

Summary

SUCCESS

No regressions found.

Participating hosts (9 -> 8)

Missing (1): bat-bmg-vm

Known issues

Here are the changes found in xkb-pr-6.17-375-618-58f684aba8289f92b467ac42f11ea6598203b62f_BAT that come from known issues:

IGT changes

Issues hit

Build changes

  • IGT: igt-xkb-116-b37ea8adf -> igt-xkb-117-4870154c2
  • Linux: xkb-6.17-267-19320f0c49ae77de8f6c80be66114cc4ec84aa5a -> xkb-pr-6.17-375-618-58f684aba8289f92b467ac42f11ea6598203b62f

igt-xkb-116-b37ea8adf: b37ea8adf
igt-xkb-117-4870154c2: 4870154c2
xkb-6.17-267-19320f0c49ae77de8f6c80be66114cc4ec84aa5a: 19320f0
xkb-pr-6.17-375-618-58f684aba8289f92b467ac42f11ea6598203b62f: 58f684a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants