-
Notifications
You must be signed in to change notification settings - Fork 111
Conversation
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1) ℹ️ |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1) ℹ️ |
I thought git 1.50 was requiring some theia api changes: eclipse-theia/theia#8623 |
I don't know exactly about changes in the API. This PR could wait for @vinokurig review as he is an expert in git. |
@benoitf extracting |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1) ℹ️ |
hi @vitaliy-guliy could you rebase your PR to try to see a green happy path ? |
f80468e
to
9e1de13
Compare
It seems something has changed for this repository, as the PR closes automatically when force-pushing to the branch. |
Signed-off-by: Vitaliy Gulyy <vgulyy@redhat.com>
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1) ℹ️
|
[crw-ci-test --rebuild] |
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
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.
please merge after 7.21 tag
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.
I've checked HTML/CSS/JSON syntax highlighting works as expected.
Also, HTML/CSS autocompletion features are working well.
For GitHub, I've checked some basic functionality. Everything seems to works fine.
|
Signed-off-by: Vitaliy Gulyy <vgulyy@redhat.com>
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
[crw-ci-test --rebuild] |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
[crw-ci-test --rebuild] |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
@ericwill curious: why did you merge with invalid happy path tests ? |
Is it a hard requirement? I saw there were no significant changes (rebase commit only) since the happy path tests last passed, so I merged. |
@ericwill yes it's like a pre-requisites |
But in this case HP is failing due to some infra/deployment issue, should we block PRs even in such a case? |
well each new build can pull upstream theia changes that breaks |
Of course, passing HappyPath tests is a requirement. |
Maybe I misunderstand, is Happy Path testing also doing some integration build/push? |
HappyPath testing builds the images with the PR changes included for testing purposes. |
This reverts commit 7f117fc.
Signed-off-by: Vitaliy Gulyy <vgulyy@redhat.com>
Signed-off-by: Vitaliy Gulyy <vgulyy@redhat.com>
… as GH action); can't popd out of a folder if we never when in there in the first place (#887) * work in tmp dir if --use-tmp-dir (not required when running as GH action) Change-Id: I59648ff7156bdce3f5361ea8e18df367eeebb924 Signed-off-by: nickboldt <nboldt@redhat.com> * can't popd out of a folder if we never when in there in the first place Change-Id: I8d7bfa5df73bb9b561380b34cd90510686fc5369 Signed-off-by: nickboldt <nboldt@redhat.com>
Signed-off-by: Vitaliy Gulyy vgulyy@redhat.com
What does this PR do?
For some built-in plugins switches to their latest versions
What issues does this PR fix or reference?
eclipse-che/che#17524
Happy Path Channel
HAPPY_PATH_CHANNEL=stable