doctest in padic_lattice_element.py gives error in current develop branch

[gh-SagnikDey92]

This is the error when doctesting in src/sage/rings/padics/padic_lattice_element.py:

File "src/sage/rings/padics/padic_lattice_element.py", line 19, in sage.rings.padics.padic_lattice_element
Failed example:
    R = ZpLF(2) # py3
Expected:
    doctest:...: FutureWarning: This class/method/function is marked as experimental. It, its functionality or its interface might change without a formal deprecation.
    See http://trac.sagemath.org/23505 for details.
Got:
    <BLANKLINE>
**********************************************************************
File "src/sage/rings/padics/padic_lattice_element.py", line 25, in sage.rings.padics.padic_lattice_element
Failed example:
    R = QpLC(2) # py3
Expected:
    doctest:...: FutureWarning: This class/method/function is marked as experimental. It, its functionality or its interface might change without a formal deprecation.
    See http://trac.sagemath.org/23505 for details.
Got:
    <BLANKLINE>
**********************************************************************
File "src/sage/rings/padics/padic_lattice_element.py", line 31, in sage.rings.padics.padic_lattice_element
Failed example:
    R = QpLF(2) # py3
Expected:
    doctest:...: FutureWarning: This class/method/function is marked as experimental. It, its functionality or its interface might change without a formal deprecation.
    See http://trac.sagemath.org/23505 for details.
Got:
    <BLANKLINE>
**********************************************************************
1 item had failures:
   3 of   5 in sage.rings.padics.padic_lattice_element
    [270 tests, 3 failures, 0.61 s]
----------------------------------------------------------------------
sage -t --warn-long 68.1 src/sage/rings/padics/padic_lattice_element.py  # 3 doctests failed
----------------------------------------------------------------------
Total time for all tests: 0.8 seconds
    cpu time: 0.6 seconds
    cumulative wall time: 0.6 seconds

Probably requires a simple change in the doctest.

[chapoton]

see #20601 for some old related ticket

[mkoeppe]

Strange that this would only be noticed now?

---

New commits:

​371c0c9

Remove repeated FutureWarnings in doctests

[roed]

With this branch, we're getting test failures on the ​patchbot where the FutureWarnings appear, so we clearly can't just remove them. I'm not sure why they appear sometime and not other times....

[mkoeppe]

Are the doctests in one block like this parallelized?

[roed]

No, they should be run in series since they're within one block.

[roed]

Another solution (that I should check with Xavier and Julian about) is to remove the experimental designation. We haven't worked on the lattice precision interface for a while, so maybe we should just think about what interface changes we want to make, make them, and then remove these warnings.

We've got a work week planned in mid April where we could look into this.

[dimpase]

Replying to roed:

With this branch, we're getting test failures on the ​patchbot where the FutureWarnings appear, so we clearly can't just remove them. I'm not sure why they appear sometime and not other times....

what is so special about this bot? These test errors are happening most everywhere, I believe I wrote about it on some of your tickets, without any replies

[gh-mwageringel]

This issue does not occur when running the long tests, but only when running the short tests, so this is not a problem on the patchbots. This might be a weird interaction between the doctest framework filtering duplicate warnings and the experimental decorator trying to avoid duplicate warnings.

This problem can be solved by reordering the doctests, so that the long test cases are executed after the short ones. Here is a branch that does this.

---

New commits:

​73e82fa

29272: reorder doctests to make long and short tests pass

[gh-kliem]

LGTM.

(Lowering the stacklevel to 3 would have worked as well, but this is so much simpler).