You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Cypress tests fail within the GitHub Actions. If you run Cypress, all tests pass
This is caused by the runner configuration of Github, which has only a limited number of cores. We can reproduce the error locally using Docker Desktop if we constrain the number of CPUs to 2.
During the first export the container awt-swiss-tml-api crashed due to a worker who was killed.
See log:
[2023-11-06 14:49:45 +0000] [7] [WARNING] Worker with pid 8 was terminated due to signal 11
Additionally, I think that the error handling introduced yesterday causes that error to fail the export. If you check older runs, you can observe that such crashes occure there aswell, but they get newer raised to the frontend. Why that‘s the case and why export still worked needs some investigation…
The text was updated successfully, but these errors were encountered:
The above explanation is wrong. I can reproduce the crash with a higher CPU count., if there are many concurrent requests to the TLM server --> see #247 there are two types of crashes
additionally 60f50c6 fixes some issues during the download of the index
Currently, the Cypress tests fail within the GitHub Actions. If you run Cypress, all tests pass
This is caused by the runner configuration of Github, which has only a limited number of cores. We can reproduce the error locally using Docker Desktop if we constrain the number of CPUs to 2.
During the first export the container
awt-swiss-tml-api
crashed due to a worker who was killed.See log:
Additionally, I think that the error handling introduced yesterday causes that error to fail the export. If you check older runs, you can observe that such crashes occure there aswell, but they get newer raised to the frontend. Why that‘s the case and why export still worked needs some investigation…
The text was updated successfully, but these errors were encountered: