-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 to k8s 1.12.6 and pkg @ HEAD #662
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@@ -17,21 +17,21 @@ required = [ | |||
name = "gopkg.in/yaml.v2" | |||
version = "v2.2.1" | |||
|
|||
[[constraint]] | |||
[[override]] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to bump go-containerregistry
to 1.12.6 for moving those back to constraint
/lgtm Thanks! 🎉 |
/lgtm |
I think this might be a legit race condition due to changes in how logs in tests with this update:
:( |
I'll do a bit of investigation, we can probably stop using those log libs in the tests entirely 😇 |
I had to pin a ton of packages to get things working. In every case I basically just pinned the version in knative/serving. This also makes a variety of updates to the e2e tests to track changes in the upstream testing libraries. Signed-off-by: Vincent Demeester <[email protected]>
/lgtm |
@@ -136,7 +134,7 @@ func TestTaskRunPipelineRunCancel(t *testing.T) { | |||
t.Errorf("Error waiting for PipelineRun `pear` to finished: %s", err) | |||
} | |||
|
|||
logger.Infof("Waiting for TaskRuns in PipelineRun %s in namespace %s to be cancelled", "pear", namespace) | |||
t.Logf("Waiting for TaskRuns in PipelineRun %s in namespace %s to be cancelled", "pear", namespace) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there's actually one problem with using t.Logf
in these integration tests: afaik the output is buffered, so if you run the test locally, you won't see the output until the test is done (e.g. maybe 5+ min later) :S
Changes
I had to pin a ton of packages to get things working. In every case I basically just pinned the version in knative/serving.
This also makes a variety of updates to the e2e tests to track changes in the upstream testing libraries.
Closes #659
cc @mattmoor I stole your commit message 😹
cc @imjasonh @bobcatfish
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
[ ] Includes docs (if user facing)See the contribution guide
for more details.
Release Notes