550
edits
Line 117: | Line 117: | ||
==== Failed scrapes ==== | ==== Failed scrapes ==== | ||
Whenever possible and at least twice a week, it is necessary to report failed tasks in | Whenever possible, and at least twice a week, it is necessary to report failed tasks in GitHub issues. | ||
If the task failure is linked to an new recipe currently being fine-tuned, the failure must be reported in the corresponding existing issue in [https://github.com/openzim/zim-requests/issues openzim/zim-request]. | If the task failure is linked to an new recipe currently being fine-tuned, the failure must be reported in the corresponding existing issue in [https://github.com/openzim/zim-requests/issues openzim/zim-request]. | ||
Line 123: | Line 123: | ||
If the task failure is linked to a recipe which already has a "Zimfarm Recipe Issue" issue opened in [https://github.com/openzim/zim-requests/issues openzim/zim-request], then a new comment must be added to the issue. | If the task failure is linked to a recipe which already has a "Zimfarm Recipe Issue" issue opened in [https://github.com/openzim/zim-requests/issues openzim/zim-request], then a new comment must be added to the issue. | ||
Otherwise, a new issue must be created in openzim/zim-request with the | Otherwise, a new issue must be created in `openzim/zim-request` at GitHub with the [https://github.com/openzim/zim-requests/issues/new/choose "Zimfarm Recipe Failure Issue" template]. The issue must first be assigned to @RavanJAltaie for first diagnosis. | ||
In both cases, the "Bug" label must be placed on the issue. | In both cases, the "Bug" label must be placed on the issue. |