Add padpo to travis-ci.#1059
Conversation
vpoulailleau
left a comment
There was a problem hiding this comment.
I agree for the || true as a starting point, though a message given by padpo is either something to be corrected in the translation or in padpo.
The content of padpo.ignore looks strange to me:
- sometimes there is a
[in the line - I would not have taken the line numbers into account, because they can be changed easily (
powrapfor instance), I would have kept the error messages
For instance, for the following padpo message:
2019-12-12 11:03:05,573 [ERROR ] pofile.py(153):display_warnings :: /tmp/padpo_e_1dtjy0/whatsnew/3.3.po: 21 [ Line length ] Line too long (90 > 79): Cet article présente les nouvelles fonctionnalités de Python 3.3, comparé à Python 3.2.
I would have kept:
[ Line length ] Line too long (90 > 79): Cet article présente les nouvelles fonctionnalités de Python 3.3, comparé à Python 3.2.
What do you think?
|
@vpoulailleau is it better? |
@JulienPalard Yes. I'm wondering about grep results with special characters at the end of the messages. But let's see in CI, since we have the |
I used -F so I don't fear that a lot. |
|
We also have to try with a failing translation (edit: it has a failing translation… or a padpo bug… 😉). BTW you made me discover a bug in |
|
The CI says: Maybe we can add a |
|
@vpoulailleau Hey a false positive for you: |
I edited my previous comment because I saw that 😉. I put this false positive so that you can test you message filtering, or maybe not 😛 |
For the moment I keep a
|| trueso it can never fail, just print the report.Closes #1057
This implements @vpoulailleau idea of whitelisting already known padpo errors so we just never introduce new ones.