xmo-odoo

An other possible effect of this is it also looks like xdist does not run all session-scoped teardowns properly when terminated early (due to either `-x` or to a C-c...

Yeah the xdist reporter would need to be able to jump back and forth, the regular report is missing useful information and the -v is hard to read (as it...

> I can imagine why pytest-xdist changed the report output, but can the pytest-xdist report changes be disabled? xdist would have to jump back and forth vertically e.g. update the...

FWIW `-v` shows per-test progress percentage, though it is verbose indeed.

Then maybe the repr for `AuthenticatedUser` when no call has been made say something like unknown / unresolved login? Obviously it's easy to trigger the resolution when you *know* that's...

> I like the `UNKNOWN` representation when login is not set. Re-set to the old code but added a fallback to `` as placeholder.

Definitely depends on #771 (as it's basically adding that one's information in an other location), which itself depends on #789. Also likely useful reading for when I tackle this: https://www.nan.fyi/svg-paths...

Also when transitioning a PR from merged to closed (because reasons) a message gets sent to both the PR being closed and its parent, which is *weird*.

After working on it a bit, there are a fair number of edge cases to retrieve the base graph (the list of all PRs in the sequence) which are *really*...

After some initial investigation it turns out that not only had I not thought to test the cross-repo case, even if I had I'd probably have missed it: the implementation...