-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Not able to generate allure report with GitHub CI #25
Comments
Hi, @MetodievIvaylo ! Could you please retry with the updated version, P.S. Is it flaky, or it reproduces always on your CI? |
I have updated the version but still have the same error. It happens every time. There are longer logs if there si something helpful.
|
Hi @MetodievIvaylo, could you please let me know the results of testing Specifically, I need to know:
|
🎉 This issue has been resolved in version 2.0.0-beta.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Hi, @noomorph. I am sorry for the late response. I have run the CI with the Node version -
|
@MetodievIvaylo can you please upgrade Node to 16.20.2, at least? |
Updating the Node to 16.20.2 fixed the problem. Thank you! 🙏 |
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
We want to use jest-allure2-report to generate a report after GitHub CI run. After the test execution allure-results folder is generated but it is just two files in it (executor.json and categories.json). In the logs we found this error listed below.
The same script locally works just fine and generates allure-results dir with all we need in it to build a report.
If you need any more information just let me know.
The text was updated successfully, but these errors were encountered: