-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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 tests wrt ginkgo 2: Add Serial decorators and change checks for serial run #8770
Update tests wrt ginkgo 2: Add Serial decorators and change checks for serial run #8770
Conversation
Skipping CI for Draft Pull Request. |
/test pull-kubevirt-e2e-k8s-1.24-sig-compute |
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.
Thanks
Few notes:
It makes KUBEVIRT_E2E_RUN_ALL_SUITES
obsolete and always true
as it will run the serial even that the parallel is failed (didnt validate but i believe this is the behavior)
(the periodic lanes are the ones that use it from what i remember)
Once junit merger is removed, additional changes should be done for the unit tests
as they run parallel and use junit merger (saw that junit merger removal is planned for other PR).
(once it is dropped, we can drop staging/src/kubevirt.io/client-go/reporter/reporter.go
and use the new built in junit-reporter instead junit-output IIRC)
Should we also remove the [Serial] manual label ?
It is not needed, but might left for helping readability ? (note that it is redundant and might be nicer to remove it)
Unless it allows to run manually only the serial ones, with focus style?
(or vice versa to skip just the serial ones when running locally)
Better that we will have options for those
hack/functests.sh
Outdated
fi | ||
|
||
functest ${test_args} ${KUBEVIRT_FUNC_TEST_GINKGO_ARGS} |
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.
don't we need to use --junit-report
( --output-dir
might be needed as well) ?
and then to remove the call to the custom reporter at tests/tests_suite_test.go
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.
@oshoval thanks for your review and the reminders.
Regarding the flag: IIRC no, we don't need to use the flag here, since it has a default value. But we can't drop it for backwards compatibility of other builds (like i.e. our d/s build), who are using this one to override the test output file name.
Regarding the custom reporter, thanks for the hint, will look into it.
9e5bc01
to
eb2331e
Compare
/test pull-kubevirt-e2e-k8s-1.24-sig-compute |
eb2331e
to
74becdc
Compare
/test pull-kubevirt-e2e-k8s-1.24-sig-compute |
See https://onsi.github.io/ginkgo/MIGRATING_TO_V2#serial-decorator Signed-off-by: Daniel Hiller <[email protected]>
Tests that check for running in serial need to get adapted to use info from the current spec, since there's no more separate running, thus the ParallelTotal will stay the same, even if the test is run in Serial mode. Signed-off-by: Daniel Hiller <[email protected]>
Signed-off-by: Daniel Hiller <[email protected]>
74becdc
to
9eb3d11
Compare
/test pull-kubevirt-e2e-k8s-1.24-sig-compute |
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.
@dhiller Thank you for the clarity !
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enp0s3 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 |
I am a bit lost about his PR and #8788 You consider this PR as a working standalone ? |
@oshoval From what I understand, this PR only prepares the ground for using Ginkgo parallel testing by just decorating with |
ah right, commits that were here where moved |
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.
Thanks
PR desc
"updates the checks for serial run and"
the word and is not needed
This is a backport of the changes introduced here: kubevirt#8770. Signed-off-by: Itamar Holder <[email protected]>
What this PR does / why we need it:
Ginkgo V2 has the decorator Serial that is designed for running tests in serial. Further the docs for parallel test support say that test results will all be captured in one output stream in Ginkgo 2.
As a preparation to use the new features this PR:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
See #8776
Release note: