* feat/perf-test: continue test when fail to get commit id
changeset.Get does not work well when the test image is in the
vendor directory because there is no kodata setup. After this
commit, failure to get the commit id will result in a
log entry instead of failing the whole test.
* Update test/mako/sidecar.go
Co-authored-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com>
Co-authored-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com>
* Various stuff around the logstream
- handle `event.Object == nil` case. We have reports of this. Strange
edgecase, but 🤷.
- add tons of tests around various cases, should raise the coverage a
bit (although, we exclude test, still should be better).
* remove chan buf
* fix spelling
* final resolution
* final resolution
* fix lint
This allows us to drop the explicit overrides in downstream repositories and it also looks so much nicer :).
I'd hope the change is non-breaking to downstream repositories, given the interface is strictly widened here.
* create a log stream that doesn't reach for pkg/test globals
* v1 can now use v2's implementation
* fix godoc
* fix self comments
* fix lints
* fix t.Error message
* guard the buffer to avoid races
* rename file to stream so that logs make more sense
* Enable golint and exclude some other generated or additional dirs
Also remove `test` ignore, since it's covered by path ignore rule.
* meh
* fixes
* more
* progressing
* further
* like a boss
It's been a longterm pet peeve of mine that we don't name test functions TestAutoTLS etc, because this
function will mutilate the names in to t-l-s, etc.
So collect a list of well known names and catch them separately.
This is not superperformant, some trie would do this job better, but since
this is test name generation, I'll let it slide :-D
* Upgrade suite types and tests
* Naively fixing upgrade suite tests
* Properly implement InstallingBase, and PreUpgradeTests
* Continual tests implemented
* UpgradeWith and PostUpgradeTests implemented
* DowngradeWith and PostDowngradeTests implemented
* zaptest.Buffer race removed
* Remove barely used testify/assert
* Ensure that VerifyContinualTests is always called if continual tests started
* Prepare tests for failure assertions
* Refactor to enable failure testing
* Prepare for failure testing
* Testing suite can fail now
* Prepare a failing test suite
* Mock testing.T implemented
* Failure testing works for single point
* Split testing code to more manageable pieces
* Tests for upgrade suite are working well
* Remove confusion about StopSignal type
A StopSignal has been splitted to 2 separate type private stoppable and
a StopEvent. StopEvent contains only elements that are essential for
implementors to use *testing.T and signalize end of stop & verify
procedure to upgrade suite.
* Introducing NewBackgroundVerification and WaitForStopEvent
Functions NewBackgroundVerification and WaitForStopEvent has
been introduced to ease implementers to write a simple setup &
verify background tests.
* Rework of "Starting continual tests"
* Removal of return value from background handler
* Move stop channel to be closer to background operation
* Remove unneeded Named interface
* Documenting public types
* Fixes to satisfy golangci-lint
* Final linting fixes
* Teach the spoofing client to support NodePort.
This is loosely based on similar logic that I added to kingress conformance testing here:
611f989aa5/test/conformance/ingress/util.go (L904-L912)
The basic idea is that in our custom dialer we look at the requested port and translate that to the service's NodePort when present.
This is in support of running Serving's e2e testing on top of KinD environments without service `type: LoadBalancer`.
* name the return values
Markus Thömmes
knative-automation
Igor Belianski
Antoine Cotten
Jean-Rémy Bancel
Victor Agababov
Zhongduo Lin (Jimmy)
Dave Protasowski
Chris Suszynski
Scott Nichols
Matt Moore
Josh Soref
Chris Suszynski