Fabian Boehm 0874dd6a96 pexpects: Fix spurious failure in generic.py
This used expect_re with a regex ending in `.*`, followed by an
`expect_prompt`.

This meant that, depending on the timing, the regex could swallow the
prompt marker, which caused extremely confusing output like

>Testing file pexpects/generic.py:Failed to match pattern: prompt 14
> ...
> OUTPUT      +1.33 ms (Line 70): \rprompt 13>functions\r\nN_, abbr,
> alias, bg, cd, [SNIP], up-or-search, vared, wait\r\n⏎
> \r⏎ \r\rprompt 14>

Yeah - it shows that "prompt 14" was in the output and it can't find
"prompt 14".

I could reproduce the failure locally when running the tests
repeatedly. I got one after 17 attempts and so far haven't been able
to reproduce it with this change applied.
2023-08-15 19:14:33 +02:00
..
2022-06-16 18:43:28 +02:00
2022-12-23 12:18:20 +01:00
2022-06-16 18:43:28 +02:00
2022-06-02 17:25:59 -07:00
2021-04-17 16:43:27 -07:00
2023-06-01 18:20:19 +02:00
2020-11-22 14:39:48 +01:00
2022-06-16 18:43:28 +02:00
2020-06-24 20:43:56 +02:00
2023-06-10 15:35:40 +02:00
2020-11-22 14:39:48 +01:00
2020-11-22 14:39:48 +01:00
2023-06-01 18:20:19 +02:00
2022-06-16 18:43:28 +02:00
2022-03-20 14:39:00 -07:00
2023-06-01 18:20:19 +02:00
2023-06-01 18:20:19 +02:00
2022-06-16 18:43:28 +02:00
2021-01-07 23:53:31 +01:00
2023-06-01 18:20:19 +02:00