Skip to content

test_tomllib.test_inline_array_recursion_limit() failed on wasm32-wasi 3.11 buildbot #108851

Closed

Description

@vstinner

test_tomllib.test_inline_array_recursion_limit() failed on wasm32-wasi 3.11 buildbot:

ERROR: test_inline_array_recursion_limit (test.test_tomllib.test_misc.TestMiscellaneous.test_inline_array_recursion_limit)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Lib/test/test_tomllib/test_misc.py", line 98, in test_inline_array_recursion_limit
    tomllib.loads(recursive_array_toml)
  File "/Lib/tomllib/_parser.py", line 102, in loads
    pos = key_value_rule(src, pos, out, header, parse_float)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Lib/tomllib/_parser.py", line 326, in key_value_rule
    pos, key, value = parse_key_value_pair(src, pos, parse_float)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Lib/tomllib/_parser.py", line 369, in parse_key_value_pair
    pos, value = parse_value(src, pos, parse_float)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Lib/tomllib/_parser.py", line 616, in parse_value
    return parse_array(src, pos, parse_float)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Lib/tomllib/_parser.py", line 420, in parse_array
    pos, val = parse_value(src, pos, parse_float)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  (...)
  File "/Lib/tomllib/_parser.py", line 416, in parse_array
    pos = skip_comments_and_array_ws(src, pos)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Lib/tomllib/_parser.py", line 278, in skip_comments_and_array_ws
    pos = skip_chars(src, pos, TOML_WS_AND_NEWLINE)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
RecursionError: maximum recursion depth exceeded

link: https://buildbot.python.org/all/#/builders/1047/builds/908

Linked PRs

Activity

  1. added 9 commits that reference this issue on Sep 3, 2023
  2. added 2 commits that reference this issue on Sep 5, 2023
  3. added a commit that references this issue on Sep 6, 2023
  4. 1 remaining item

  5. added a commit that references this issue on Sep 6, 2023
  6. added a commit that references this issue on Sep 6, 2023
  7. added a commit that references this issue on Sep 8, 2023
  8. added 2 commits that reference this issue on Sep 29, 2023
  9. markshannon commented on Nov 18, 2023

    @markshannon
    Member

    I don't understand what's going on here.
    Why does the test fail?
    Hacking the tests does not seem to be the right solution. Why not fix the underlying problem, or at least triage it first?

  10. markshannon commented on Nov 18, 2023

    @markshannon
    Member

    My mistake. I didn't see the all important 3.11 part.
    Still, we ought to record what the problem is on the issue, before fixing it.

  11. markshannon commented on Nov 18, 2023

    @markshannon
    Member

    So, why change 3.13 and 3.12, if this is a 3.11 issue?

  12. vstinner commented on Nov 27, 2023

    @vstinner
    MemberAuthor

    So, why change 3.13 and 3.12, if this is a 3.11 issue?

    First I saw the issue on 3.11, but in fact the 3 branches were affectected: 3.11, 3.12 and main.

    @markshannon: Did you reopen the issue because you want to make changes?

  13. brettcannon commented on Dec 14, 2023

    @brettcannon
    Member

    Since all the buildbots are passing, I'm closing the issue as fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    3.11only security fixesOS-wasitestsTests in the Lib/test dir

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions