[che-dev] Status of E2E tests check of Eclipse Che repo PR

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[che-dev] Status of E2E tests check of Eclipse Che repo PR

From: Dmytro Nochevnov <dnochevn@xxxxxxxxxx>
Date: Mon, 9 Dec 2019 11:43:51 +0200
Delivered-to: che-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/che-dev>
List-help: <mailto:che-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/che-dev>, <mailto:che-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/che-dev>, <mailto:che-dev-request@eclipse.org?subject=unsubscribe>

Hello everyone.

FYI: Che QE team has decided to unite happy path tests and java selenium tests into one directory named tests.

Please, take changes from Eclipse Che master branch so that ci-integration-tests and crw-ci-e2e-happy-path-tests PR checks work normally.

E2E Happy path tests check failure can be recognized by the following error message in jenkins job console log:

ERROR: /var/lib/jenkins/workspace/Multiuser-Che-PR-check-E2E-Happy-path-tests-against-k8s@script/e2e/jenkins/crw-ci/pr-check/k8s/Jenkinsfile not found
Finished: FAILURE

With best regards,

Dmytro Nochevnov

Senior Quality Engineer

Che QE team

Prev by Date: Re: [che-dev] che-bot PR comments - annoying or useful?
Next by Date: [che-dev] Reminder Community Call today (December 9th)
Previous by thread: [che-dev] Request for review: plugin broker refactoring
Next by thread: [che-dev] Status of E2E tests check of Eclipse Che repo PR
Index(es):
- Date
- Thread

Breadcrumbs