-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 screencatcher in the e2e folder for avoiding errors #14394
Conversation
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
fs.mkdirSync(executionScreenCastErrorsDir); | ||
} | ||
|
||
let errorLogFilePath: string = screenshotPath.replace('.png', '.txt'); |
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.
Here we can just add .txt
, or, more obvious, .error.log
to the screenshotPath, to have file name like the follow:
0010002--(10:04:38.853): Open workspace.png.error.log
PR commonly looks good. I would only ask you to wait on results of PR check on CRW Jenkins CI before merging. |
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
crw-ci-test |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com>
@Ohrimenko1988: there is Happy path tests error #14394 (comment):
|
Oh, you have fixed it recently. |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
ci-test |
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
ci-test |
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com> * Use eclipse/che-e2e:nightly to run Happy path tests on Jenkins CI Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com> * Decrease Happy path tests execution build timeout to 20 minutes Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com> * Use bujhtr5555/che-e2e:latest to check fixup Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com> * Fix che start command Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com> * Update screencatcher in the e2e folder for avoiding errors (#14394) * Fix mistake in the "activateBreakpoint" method Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com> * Rework method for enabling debug breakpoint Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com> * Cleanup code Signed-off-by: Ihor Okhrimenko <iokhrime@redhat.com> * Run tests from docker image Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com> * Run local tests mounted to docker image Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com> * Check tests with cypress/browsers:node8.9.3-chrome73 Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com> * check with eclipse/che-e2e:nightly Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com> * Run tests from inside eclipse/che-e2e:nightly Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com> * Check local e2e tests Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com> * Pre-pull eclipse/che-e2e:nightly Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com> * Check local tests with updated eclipse/che-e2e:nightly Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com>
Signed-off-by: Ihor Okhrimenko iokhrime@redhat.com
What does this PR do?
Update screencatcher in the e2e folder for avoiding errors
If screenshots store without errors, all works as before
If error happens, the error interrupts and stack trace stores in the separated folder and file
What issues does this PR fix or reference?
Issue: #14384
Release Notes
Docs PR