547
edits
Difference between revisions of "Content team"
Jump to navigation
Jump to search
→"Zimfarm Recipe Failure Issue" issues
| Line 127: | Line 127: | ||
In both cases, the "Bug" label must be placed on the issue. | In both cases, the "Bug" label must be placed on the issue. | ||
==== "Zimfarm Recipe Failure Issue" issues ==== | ==== Diagnose "Zimfarm Recipe Failure Issue" issues ==== | ||
You may do the first diagnosis only if the issue is assigned to you. If the issue is assigned to someone else, please ask for permission first. This rule can be bypassed for obvious reasons is the person is on long leave, sick, ... | You may do the first diagnosis only if the issue is assigned to you. If the issue is assigned to someone else, please ask for permission first. This rule can be bypassed for obvious reasons is the person is on long leave, sick, ... | ||
| Line 133: | Line 133: | ||
To diagnose "Zimfarm Recipe Issue", following criteria have to be analyzed: | To diagnose "Zimfarm Recipe Issue", following criteria have to be analyzed: | ||
# Is this the first failure of the recipe in a row? | |||
# Do we have a previous task that worked well? | |||
# Do we miss an obvious error message in the scraper log that indicates the recipe is doomed to fail if ran again? | |||
If the answer is "yes" to all three questions, then the recipe must be requested again, this might have been a temporary failure. | |||
Otherwise, either the recipe parameters have to be adjusted if the fix is obvious (e.g. "Title is too long error", ...) and the recipe requested again, or the issue must be raised to @benoit74 for analysis via [https://github.com/openzim/zim-requests/issues an issue at GiHub]. | |||
Otherwise, either the recipe parameters have to be adjusted if the fix is obvious (e.g. "Title is too long error", ...) and the recipe requested again, or the issue must be raised to | |||
==== First diagnosis of "Zimfarm Task Duration Issue" issues ==== | ==== First diagnosis of "Zimfarm Task Duration Issue" issues ==== | ||