Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-35935

unittest/unittest_test StackTraceForAssertion failed

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.0
    • Component/s: Build
    • Labels:
      None
    • Environment:
      GCC 8.1.1 compiler, glibc 2.27.9000
      same result on all supported architectures,
    • ALL
    • Hide

      $ cat build-options
      -j4 --use-system-pcre --use-system-boost --use-system-snappy --use-system-valgrind --use-system-zlib --use-system-stemmer --use-system-tcmalloc --use-system-yaml --mmapv1=on --wiredtiger=on --ssl --nostrip --disable-warnings-as-errors --variables-files=variables.list

      $ scons $(cat build-options) build/fedora/mongo/unittest/unittest_test --opt=off

      Show
      $ cat build-options -j4 --use-system-pcre --use-system-boost --use-system-snappy --use-system-valgrind --use-system-zlib --use-system-stemmer --use-system-tcmalloc --use-system-yaml --mmapv1=on --wiredtiger=on --ssl --nostrip --disable-warnings-as-errors --variables-files=variables.list $ scons $(cat build-options) build/fedora/mongo/unittest/unittest_test --opt=off

      unittest/unittest_test fails in MongoDB 4.0 - output is attached.

      Or is something special needed to be able to print stacktrace properly?

            Assignee:
            andrew.morrow@mongodb.com Andrew Morrow (Inactive)
            Reporter:
            mskalick Marek Skalický
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: