Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-126225

tst_QSharedMemory::useTooMuchMemory(POSIX) timeout on linux arm64 in CI

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • P2: Important
    • None
    • 6.8
    • Core: Other
    • None
    • Linux/Other display system
    • 194318328 (dev), 217d2839b (6.8)

    Description

      https://testresults.qt.io/coin/integration/qt/qtbase/tasks/web_qt_qtbase_1717873877956
      https://testresults.qt.io/coin/api/log/qt/qtbase/19e0e2b702bec6c2fd6a8c9197973b12b720e3c7/LinuxUbuntu_24_04aarch64LinuxUbuntu_24_04aarch64GCCqtci-linux-Ubuntu-24.04-aarch64-50-57847fInsignificantTests_TestOnly/860d6584b095137001acae3e0e2883e9199fb9ac/test_1717873881/log.txt.gz

      agent:2024/06/08 19:48:41 build.go:404: 98: SKIP   : tst_QSharedMemory::simpleProcessProducerConsumer(SystemV-T:5 processes) This test is unstable: QTBUG-25655
      agent:2024/06/08 19:48:41 build.go:404: 98:    Loc: [/home/qt/work/qt/qtbase/tests/auto/corelib/ipc/qsharedmemory/tst_qsharedmemory.cpp(867)]
      agent:2024/06/08 19:53:41 build.go:404: 98: 
      agent:2024/06/08 19:53:41 build.go:404: 98:          useTooMuchMemory function time: 300000ms, total time: 301912ms
      agent:2024/06/08 19:53:41 build.go:404: 98: 
      agent:2024/06/08 19:53:41 build.go:404: 98: === Stack trace ===
      agent:2024/06/08 19:53:42 build.go:404: 98: Could not attach to process.  If your uid matches the uid of the target
      agent:2024/06/08 19:53:42 build.go:404: 98: process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
      agent:2024/06/08 19:53:42 build.go:404: 98: again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
      agent:2024/06/08 19:53:42 build.go:404: 98: ptrace: Inappropriate ioctl for device.
      agent:2024/06/08 19:53:42 build.go:404: 98: QFATAL : tst_QSharedMemory::useTooMuchMemory(POSIX) Test function timed out
      agent:2024/06/08 19:53:42 build.go:404: 98: FAIL!  : tst_QSharedMemory::useTooMuchMemory(POSIX) Received a fatal error.
      agent:2024/06/08 19:53:42 build.go:404: 98: Totals: 175 passed, 1 failed, 30 skipped, 0 blacklisted, 302651ms
      agent:2024/06/08 19:53:42 build.go:404: 98: ********* Finished testing of tst_QSharedMemory *********
      agent:2024/06/08 19:53:42 build.go:404: 98: === End of stack trace ===
      agent:2024/06/08 19:53:42 build.go:404: 98: Received signal 6 (SIGABRT)
      agent:2024/06/08 19:53:42 build.go:404: 98:          useTooMuchMemory function time: 300739ms, total time: 302651ms
      agent:2024/06/08 19:53:42 build.go:404: 98: 
      agent:2024/06/08 19:53:42 build.go:404: 98: === Stack trace ===
      agent:2024/06/08 19:53:43 build.go:404: 98: Could not attach to process.  If your uid matches the uid of the target
      agent:2024/06/08 19:53:43 build.go:404: 98: process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
      agent:2024/06/08 19:53:43 build.go:404: 98: again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
      agent:2024/06/08 19:53:43 build.go:404: 98: ptrace: Inappropriate ioctl for device.
      agent:2024/06/08 19:53:43 build.go:404: 98: === End of stack trace ===
      agent:2024/06/08 19:53:44 build.go:404: 98: qt-testrunner.py     INFO: Test process exited with code: -6
      agent:2024/06/08 19:53:44 build.go:404: 98: qt-testrunner.py     INFO: Parsed XML file /home/qt/work/testresults/tst_qsharedmemory-1717876120024.xml in 0.003 seconds
      agent:2024/06/08 19:53:44 build.go:404: 98: qt-testrunner.py     INFO: Found 205 passes and 1 failures
      

      Attachments

        Issue Links

          For Gerrit Dashboard: QTBUG-126225
          # Subject Branch Project Status CR V

          Activity

            People

              cnn Qt Core & Network
              liaqi Liang Qi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes