Closed shubham-pampattiwar closed 2 months ago
/retest-required
Remaining retests: 0 against base HEAD b0e0d121d272c0bcbe75dcb4008fe7cb7bb13904 and 2 for PR HEAD 9c58efdd7564d41add6b0b9f67d29520959462a8 in total
/retest-required
Remaining retests: 0 against base HEAD b0e0d121d272c0bcbe75dcb4008fe7cb7bb13904 and 2 for PR HEAD 9c58efdd7564d41add6b0b9f67d29520959462a8 in total
I think this needs to be updated https://github.com/openshift/oadp-operator/blob/master/tests/e2e/virt_backup_restore_suite_test.go#L245
after rebase, should not error anymore, right?
unless there's merge conflict, rebasing should not be necessary. retest should test against new base ref merged with pr.
I think this needs to be updated https://github.com/openshift/oadp-operator/blob/master/tests/e2e/virt_backup_restore_suite_test.go#L245
ya agree. seems to be successful now.. if expected, need to remove this RestoreErr
/retest-required
Remaining retests: 0 against base HEAD b0e0d121d272c0bcbe75dcb4008fe7cb7bb13904 and 2 for PR HEAD 9c58efdd7564d41add6b0b9f67d29520959462a8 in total
/retest
/retest
/test 4.14-e2e-test-aws
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: kaovilai, mateusoliveira43, shubham-pampattiwar, sseago, weshayutin
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@shubham-pampattiwar: all tests passed!
Full PR test history. Your PR dashboard.
Why the changes were made
Go mod and CRD updates required due to Velero rebase
How to test the changes made
Any kind of E2E sanity testing would be helpful here !