The test proper coloring for overdue task from an hour ago fails,
even though the task is properly colored. This is because the blue color
gets upgraded to blue color in 256-color scheme, and hence is
represented with 38;5;4m instead of 34m.
Support both representations of the blue color in the given test.
This commit updates all tests to enforce the Python3 executable. This is
necessary because the `assertRegex` function we use was renamed to this
name only in Python 3.2 [1]
For reference:
s;/usr/bin/env python;/usr/bin/env python3;g
[1]: https://docs.python.org/3/library/unittest.html#unittest.TestCase.assertRegex
- This is a bug in Color.cpp, not in the color.rules.t script, and the symptoms
of this bug are 256-color usage when 16-colors are expected. The Color::blend
method auto-upgradeѕ from 16 to 256, and may be the culprit. This bug is not
important enough to fix now.
- Problem was that Linux has been upgrading 16-color output, and the test was
based on observed output, which looks correct, but actually isn't.
We may end up marking these tests as expeected to fail, because they are not
important.
