Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Let "depoly-setup.sh" and "undeploy.sh" fail on error #686

Merged

Conversation

thom311
Copy link
Contributor

@thom311 thom311 commented Apr 19, 2024

Ignoring errors seems not best. It can make it harder to find problems with the script.

If a command in the script is known to fail for valid reasons, then that should be treated specially (for example, with || :). By default, treat any unexpected failure as fatal and propagate the failure to the caller.

Fixes: 8844150 ('Add RBAC for cluster resource')

CC: @pliurh

Copy link

Thanks for your PR,
To run vendors CIs use one of:

  • /test-all: To run all tests for all vendors.
  • /test-e2e-all: To run all E2E tests for all vendors.
  • /test-e2e-nvidia-all: To run all E2E tests for NVIDIA vendor.

To skip the vendors CIs use one of:

  • /skip-all: To skip all tests for all vendors.
  • /skip-e2e-all: To skip all E2E tests for all vendors.
  • /skip-e2e-nvidia-all: To skip all E2E tests for NVIDIA vendor.
    Best regards.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 8755557051

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.02%) to 38.404%

Totals Coverage Status
Change from base Build 8738593529: 0.02%
Covered Lines: 4817
Relevant Lines: 12543

💛 - Coveralls

Copy link
Collaborator

@SchSeba SchSeba left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Collaborator

@adrianchiris adrianchiris left a comment

Choose a reason for hiding this comment

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

lgtm

@SchSeba
Copy link
Collaborator

SchSeba commented Aug 19, 2024

Hi @thom311 can you please do a force push I am not able to trigger the k8s lane for some reason

Ignoring errors seems not best. It can make it harder to find problems
with the script.

If a command in the script is known to fail for valid reasons, then that
should be treated specially (for example, with `|| :`). By default,
treat any unexpected failure as fatal and propagate the failure to the
caller.

Fixes: 8844150 ('Add RBAC for cluster resource')
@adrianchiris
Copy link
Collaborator

/test-all

@coveralls
Copy link

Pull Request Test Coverage Report for Build 10455381530

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 44.999%

Totals Coverage Status
Change from base Build 10454628601: 0.0%
Covered Lines: 6533
Relevant Lines: 14518

💛 - Coveralls

@SchSeba
Copy link
Collaborator

SchSeba commented Aug 27, 2024

all green merging nice work!

@SchSeba SchSeba merged commit 34dcef5 into k8snetworkplumbingwg:master Aug 27, 2024
14 checks passed
@thom311 thom311 deleted the th/script-exit-on-error branch August 28, 2024 06:08
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