Closed RhCheGithubBot closed 4 years ago
@ibuziuk Hi, now the check is failing on compilation error. Will you have time to take a look?
@ibuziuk Thank you for the fix, now we are failing on https://github.com/eclipse/che/issues/18075
@Katka92 yeah, commented in the upstream issue - https://github.com/eclipse/che/issues/18075#issuecomment-705487253
[test]
[test]
[test]
@Katka92 @ScrewTSW could you please take a look at the failing test:
11 passing (4m)
1 failing
1) Java Maven test
Validation of workspace build and run
Run command 'maven build':
Error: Timeout of 120000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/tmp/rh-che/local_tests/node_modules/e2e/dist/tests/devfiles/JavaMaven.spec.js)
[test]
[test]
[test]
The test running build
command was skipped in upstream. It seems it is not propagated here. We'll check that.
So, the root cause is that the upstream nightly test image was not updated for 4 days, the reason is FATAL: Vault credentials not found for 'devtools-osio-ci/quay-eclipse-che-credentials'
. So we don't have the latest changes in place and we can not test that properly.
The image was updated manually, re-running the tests. [test]
deployment: https://rhche-prcheck-1969.apps.che-dev.x6e0.p1.openshiftapps.com console: https://ci.centos.org/view/Devtools/job/devtools-rh-che-rh-che-prcheck-dev.rdu2c.fabric8.io/2962/console
Tracking changes for fixing compatibility with upstream 7.19.0-SNAPSHOT. This PR was created automatically by Jenkins from job devtools-rh-che-rh-che-compatibility-test-dev.rdu2c.fabric8.io