-
Notifications
You must be signed in to change notification settings - Fork 411
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
Update goss #1680
base: main
Are you sure you want to change the base?
Update goss #1680
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
b251e8e
to
49253ec
Compare
/test ? |
@sivchari: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/test pull-azure-vhds |
I don't know why this CI is broken {
"error": {
"code": 401,
"message": "Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.",
"errors": [
{
"message": "Login Required.",
"domain": "global",
"reason": "required",
"location": "Authorization",
"locationType": "header"
}
],
"status": "UNAUTHENTICATED",
"details": [
{
"@type": "type.googleapis.com/google.rpc.ErrorInfo",
"reason": "CREDENTIALS_MISSING",
"domain": "googleapis.com",
"metadata": {
"method": "compute.v1.ImagesService.Get",
"service": "compute.googleapis.com"
}
}
]
}
} |
Signed-off-by: sivchari <[email protected]>
Signed-off-by: sivchari <[email protected]>
Signed-off-by: sivchari <[email protected]>
Signed-off-by: sivchari <[email protected]>
Signed-off-by: sivchari <[email protected]>
Signed-off-by: sivchari <[email protected]>
Looking at the GCP failure I can see there are actually 3 goss failures, e.g.:
Search for I don't understand why those are failing with this change though. I suspect something has changed in Goss that now makes this fail but not sure what or when exactly. I wonder if it might make sense to first update to the latest |
Signed-off-by: sivchari <[email protected]>
@AverageMarcus |
All test are passed, so the minor upgradeing affects something. |
Signed-off-by: sivchari <[email protected]>
|
Signed-off-by: sivchari <[email protected]>
Signed-off-by: sivchari <[email protected]>
Signed-off-by: sivchari <[email protected]>
|
Signed-off-by: sivchari <[email protected]>
Signed-off-by: sivchari <[email protected]>
/retest |
Looks like just need to fix Goss running on Windows now:
|
🤔 That's not the correct path. The |
ah-ha! I think we need to remove all the references to |
@AverageMarcus |
Signed-off-by: sivchari <[email protected]>
Signed-off-by: sivchari <[email protected]>
Signed-off-by: sivchari <[email protected]>
Signed-off-by: sivchari <[email protected]>
Signed-off-by: sivchari <[email protected]>
I totally understand why the test must be failed when the version is v0.4.0 later. This line check if the goss is alpha. Then, when the OS is windows, we required GOSS_USE_ALPHA = 1 to run the render and other command. But after v0.4.x, the |
@sivchari: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Change description
Updated goss version and correct release url
Related issues
Additional context