-
Notifications
You must be signed in to change notification settings - Fork 286
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
chore: Add the faas-js-runtime to the testing suite. #377
chore: Add the faas-js-runtime to the testing suite. #377
Conversation
[test] |
2 similar comments
[test] |
[test] |
@zmiklank not sure what is going on with the tests. doesn't look like it has anything to do with what I've added |
We are seeing issues with RHEL-based CI due to some of the infrastructure used for the tests getting refreshed over the coming week or two. I expect we will have to wait until that is done before the tests have a chance to get green. What I find more troubling is that I do not see client test case results in the test runs that did pass. The only mention of them is this
Rerunning the tests locally with more versbosity:
This seems like a bug and the client cases are ignored completely. Also an error like this should have at least failed the whole test suite. |
Immediate issues in the client test case runner will be fixed in #378 |
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.
LGTM
Now that #378 is merged, please rebase and lets try this once more. |
The faas-js-runtime is the framework which runs and invokes node.js serverless functions for Openshift Serverless.
2e10ab4
to
1834101
Compare
rebased |
[test] |
Looks like these failures are unrelated to the client tests |
The tests fail with Looking at the changes it seems like the test case wrapper function (something like https://github.com/sclorg/s2i-nodejs-container/blob/master/test/test-lib-nodejs.sh#L392) is missing. |
Ah yes, that part wasn't there when we added the previous clients. Added the function |
[test] |
Looks like the failures are unrelated to this PR. |
Looks like more pino failures :/ Let me rerun failed jobs to see if they managed to change in the meantime. |
Since the failure doesn't have to do with this PR, could we get this merged and I will create another issue for our team to look at regarding the pinot tests? |
RHEL8 tests for Node 18 failing on faas-js:
Node 16 on RHEL8 failed due to what looks like infra issues, will try rerunning once more. |
@pkubatrh is there a way to test that RHEL8 node 18 image locally? i tried to do this |
Also wanted to mention that i created an issue for the pino failures: #381 |
[test] |
@lholmquist You likely defaulted to the authenticated red hat registry (registy.redhat.io), try |
Rerunning RHEL8 tests to see if faas-js manages to pass. |
🎉 |
The faas-js-runtime is the framework which runs and invokes node.js serverless functions for Openshift Serverless.