[Bug 1916749] Re: plf-colony simple.cc test fails with "stderr: dis_syslink(ppc)(theInstr)" on ppc64el with glibc 2.33

[Dimitri John Ledkov]

** Also affects: valgrind (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: glibc (Ubuntu)
       Status: New => Incomplete

** Changed in: plf-colony (Ubuntu)
       Status: New => Incomplete

** Changed in: valgrind (Ubuntu)
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to valgrind in Ubuntu.
https://bugs.launchpad.net/bugs/1916749

Title:
  plf-colony simple.cc test fails with "stderr:
  dis_syslink(ppc)(theInstr)" on ppc64el with glibc 2.33

Status in glibc package in Ubuntu:
  Incomplete
Status in plf-colony package in Ubuntu:
  Incomplete
Status in valgrind package in Ubuntu:
  In Progress

Bug description:
  The simple.cc test of plf-colony fails on ppc64el with "stderr:
  dis_syslink(ppc)(theInstr)" if glibc 2.33 is in use (hence on
  hirsute).

  The test doesn't break entirely, but two lines are written to stderr that make the overall test to fail:
  "
  autopkgtest [06:59:07]: test simple-gcc-valgrind:
  dis_syslink(ppc)(theInstr)
  dis_syslink(ppc)(theInstr)
   0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
  "

  This turned out to be the root problem for the blocked transition of valgrind:
  valgrind | 1:3.16.1-1ubuntu3   | hirsute-proposed
  https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#valgrind
  The autopackage test fails for ppc64el only:
  "autopkgtest for plf-colony/6.12-1: amd64: Pass, arm64: Pass, armhf: Pass, ppc64el: Regression ♻ , s390x: Pass"

  And the logs point to the above mentioned issue:
  https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/ppc64el/p/plf-colony/20210224_065926_061e7@/log.gz
  "
  autopkgtest [06:59:07]: test simple-gcc-valgrind: g++ -Wall -o "$AUTOPKGTEST_TMP"/⁊ debian/tests/simple.cc && valgrind --error-exitcode=1 -q "$AUTOPKGTEST_TMP"/⁊ autopkgtest [06:59:07]: test simple-gcc-valgrind: [-----------------------
  dis_syslink(ppc)(theInstr)
  dis_syslink(ppc)(theInstr)
  0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 autopkgtest [06:59:09]: test simple-gcc-valgrind: -----------------------] autopkgtest [06:59:10]: test simple-gcc-valgrind:  - - - - - - - - - - results - - - - - - - - - - simple-gcc-valgrind  FAIL stderr: dis_syslink(ppc)(theInstr) autopkgtest [06:59:10]: test simple-gcc-valgrind:  - - - - - - - - - - stderr - - - - - - - - - - dis_syslink(ppc)(theInstr) dis_syslink(ppc)(theInstr) autopkgtest [06:59:11]: @@@@@@@@@@@@@@@@@@@@ summary simple-gcc           PASS simple-clang         PASS simple-gcc-valgrind  FAIL stderr: dis_syslink(ppc)(theInstr)
  "

  This is not a regression in the updated valgrind package itself
  (3.16.1-1ubuntu3) since it also happens on groovy if one just upgrades
  glibc to 2.33 (taken from hirsute).

  Ideally this should be fixed in glibc 2.33, but due to the complexity a different approach will be taken and the simple.cc test in plf-colony adjusted like this:
  # g++ -Wall -o "$AUTOPKGTEST_TMP"/⁊ debian/tests/simple.cc && valgrind --error-exitcode=1 -q "$AUTOPKGTEST_TMP"/⁊ 2>/dev/null
  0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
  (by making sure that the return code is still valid and true)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1916749/+subscriptions