LivelyKernel / LivelyKernel/lively.next
Get more information about failing CI runs
@linusha is already working on this.
Since Jun 3, 2024.
- Dominant language
- JavaScript
- Stars
- 90
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Currently, when tests fail in CI and we cannot reproduce the failure locally, we are more or less unable to gather any significant information about what the problem is.
There are two aspects to this:
1. Error messages from within lively or the output of failing tests should be retrieved. This can be achieved with simple changes to the test runner, the testing subserver and the CI scripts.
2. Sometimes, for example in the cases of #1524, this information would not suffice. What is needed there would be to capture the logs of the console of the chrome instance running the headless tests. More research is needed to find a suitable solution for this problem.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.