Uploaded image for project: 'RHEL Testing'
  1. RHEL Testing
  2. RHELTEST-231

LTP: openposix - pthread_create_3-2.run-test: symbol lookup error: ./pthread_create_3-2.run-test: undefined symbol: exit, version GLIBC_2.2.5

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • rhel-kernel-ft

      This issue was originally created at 2024-10-11T06:07:24.147Z as a Gitlab issue:
      https://gitlab.com/redhat/centos-stream/tests/kernel/kernel-tests/-/issues/2031

      1. Snippet of test failure

      conformance/interfaces/pthread_create/pthread_create_3-2: execution: UNRESOLVED: Output:
      [06:19:15]
      Growing down stack started upon 0x7f289c0cbea8 and we are currently down to 0x7f289c0c7e98
      [06:19:15]
      Test starting
      Stack tests will be executed.
      Sched tests will be executed.
      [06:19:15]
      System abilities:
      [06:19:15]
      TSA: 200809
      [06:19:15]
      TSS: 200809
      [06:19:15]
      TPS: 200809
      [06:19:15]
      pagesize: 4096
      [06:19:15]
      min stack size: 16384
      [06:19:15]
      WARNING: The TPS option is claimed to be supported but setscope fails
      [06:19:15]
      WARNING: The TPS option is claimed to be supported but setscope fails
      [06:19:15]
      WARNING: The TPS option is claimed to be supported but setscope fails
      [06:19:15]
      WARNING: The TPS option is claimed to be supported but setscope fails
      [06:19:15]
      WARNING: The TPS option is claimed to be supported but setscope fails
      [06:19:15]
      WARNING: The TPS option is claimed to be supported but setscope fails
      [06:19:15]
      WARNING: The TPS option is claimed to be supported but setscope fails
      [06:19:15]
      WARNING: The TPS option is claimed to be supported but setscope fails
      [06:19:15]
      WARNING: The TPS option is claimed to be supported but setscope fails
      [06:19:15]
      All 33 thread attribute objects were initialized

      [06:19:15]


      [06:19:15]
      Starting test with scenario (0): default
      [06:19:15]
      Growing down stack started upon 0x7f289c0cbea8 and we are currently down to 0x7f289c0c7e98
      [06:19:15]


      [06:19:15]
      Starting test with scenario (1): detached
      [06:19:15]
      Growing down stack started upon 0x7f289c0cbea8 and we are currently down to 0x7f289c0c7e98
      [06:19:15]


      [06:19:15]
      Starting test with scenario (2): Explicit sched
      [06:19:15]
      Growing down stack started upon 0x7f289c0cbea8 and we are currently down to 0x7f289c0c7e98
      [06:19:15]


      [06:19:15]
      Starting test with scenario (3): FIFO Policy
      [06:19:15]
      Growing down stack started upon 0x7f289c0cbea8 and we are currently down to 0x7f289c0c7e98
      [06:19:15]


      [06:19:15]
      Starting test with scenario (4): RR Policy
      [06:19:15]
      Growing down stack started upon 0x7f289c0cbea8 and we are currently down to 0x7f289c0c7e98
      [06:19:15]


      [06:19:15]
      Starting test with scenario (5): Max sched param
      [06:19:15]
      Growing down stack started upon 0x7f289c0cbea8 and we are currently down to 0x7f289c0c7e98
      [06:19:15]


      [06:19:15]
      Starting test with scenario (6): Min sched param
      [06:19:15]
      Growing down stack started upon 0x7f289c0cbea8 and we are currently down to 0x7f289c0c7e98
      [06:19:15]


      [06:19:15]
      Starting test with scenario (7): Alternative contension scope
      [06:19:15]
      Growing down stack started upon 0x7f289c0cbea8 and we are currently down to 0x7f289c0c7e98
      [06:19:15]


      [06:19:15]
      Starting test with scenario (8): Alternative stack
      [06:19:15]


      [06:19:15]
      Starting test with scenario (9): No guard size
      [06:19:15]
      Growing down stack started upon 0x7f289c0cbea8 and we are currently down to 0x7f289c0c7e98
      [06:19:15]


      [06:19:15]
      Starting test with scenario (10): 1p guard size
      [06:19:15]
      Growing down stack started upon 0x7f289c0cbea8 and we are currently down to 0x7f289c0c7e98
      [06:19:15]


      [06:19:15]
      Starting test with scenario (11): Min stack size
      [06:19:16]


      [06:19:16]
      Starting test with scenario (12): Min stack size, no guard
      ./pthread_create_3-2.run-test: symbol lookup error: ./pthread_create_3-2.run-test: undefined symbol: exit, version GLIBC_2.2.5
      [06:19:16]
      The child process returned: 127
      [06:19:16]
      Test ../../../conformance/interfaces/pthread_create/3-2.c unresolved: got -1 (Unknown error -1) on line 470 (An unexpected error occured
      )

      1. Test logs on DataWarehouse
        https://beaker.engineering.redhat.com/recipes/17164954#task185051781
      1. DataWarehouse issue
      1. Additional details

      I've resubmitted the failed job several times, and the same issue did not reproduce:
      1. https://beaker.engineering.redhat.com/recipes/17193828#task185214504
      2. https://beaker.engineering.redhat.com/jobs/9997652
      3. https://beaker.engineering.redhat.com/jobs/9993440

      **In case opening the links above result in a 404 page on DataWarehouse, please
      make sure you are [correctly logged into DataWarehouse via Red Hat SSO](
      https://cki-project.org/l/datawarehouse-404).**

              pifang@redhat.com Ping Fang
              shichen@redhat.com Shizhao Chen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: