[Bug 1997475] [NEW] FTBFS: tests fail on s390x due to incorrect regexp on /proc/cpuinfo

Andreas Hasenack 1997475 at bugs.launchpad.net
Tue Nov 22 17:22:35 UTC 2022


Public bug reported:

git commit 29fb2ec384a867ca577335a12f4b45c184e7b642, present in 2.38.0
and later, introduced a function that gets the number of cores from
/proc/cpuinfo. It essentially does this:

    do { local @ARGV='/proc/cpuinfo'; return
scalar(grep(/^processor\s*:/, <>)); } if -r '/proc/cpuinfo';

On s390x, the ^processor lines are like this:

processor 0: version = FF,  identification = 148F67,  machine = 2964

In other arches (I checked amd64, armhf and arm64), they are like this
instead:

processor       : 0

As a result, that function is returning 0 on s390x, and that value is
used for the number of jobs the script should execute. Since it's zero,
it exits without doing anything, and that breaks the test and the
build[3] on s390x.

1. https://github.com/git/git/commit/29fb2ec384a867ca577335a12f4b45c184e7b642
2. https://github.com/git/git/commit/29fb2ec384a867ca577335a12f4b45c184e7b642#diff-e7042d714d4be11a06d153e6f2daeb3c3a9766b972522baab8ba113b962086cfR574
3. https://launchpadlibrarian.net/635348769/buildlog_ubuntu-lunar-s390x.git_1%3A2.38.1-1ubuntu1_BUILDING.txt.gz

** Affects: git (Ubuntu)
     Importance: Undecided
     Assignee: Andreas Hasenack (ahasenack)
         Status: In Progress


** Tags: ftbfs

** Changed in: git (Ubuntu)
     Assignee: (unassigned) => Andreas Hasenack (ahasenack)

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

** Description changed:

  git commit 29fb2ec384a867ca577335a12f4b45c184e7b642, present in 2.38.0
  and later, introduced a function that gets the number of cores from
  /proc/cpuinfo. It essentially does this:
  
-     do { local @ARGV='/proc/cpuinfo'; return
- scalar(grep(/^processor\s*\d*\s*:/, <>)); } if -r '/proc/cpuinfo';
- 
+     do { local @ARGV='/proc/cpuinfo'; return
+ scalar(grep(/^processor\s*:/, <>)); } if -r '/proc/cpuinfo';
  
  On s390x, the ^processor lines are like this:
  
  processor 0: version = FF,  identification = 148F67,  machine = 2964
  
- 
- In other arches (I checked amd64, armhf and arm64), they are like this instead:
+ In other arches (I checked amd64, armhf and arm64), they are like this
+ instead:
  
  processor       : 0
  
- 
- As a result, that function is returning 0 on s390x, and that value is used for the number of jobs the script should execute. Since it's zero, it exits without doing anything, and that breaks the test and the build[3] on s390x.
- 
+ As a result, that function is returning 0 on s390x, and that value is
+ used for the number of jobs the script should execute. Since it's zero,
+ it exits without doing anything, and that breaks the test and the
+ build[3] on s390x.
  
  1. https://github.com/git/git/commit/29fb2ec384a867ca577335a12f4b45c184e7b642
  2. https://github.com/git/git/commit/29fb2ec384a867ca577335a12f4b45c184e7b642#diff-e7042d714d4be11a06d153e6f2daeb3c3a9766b972522baab8ba113b962086cfR574
  3. https://launchpadlibrarian.net/635348769/buildlog_ubuntu-lunar-s390x.git_1%3A2.38.1-1ubuntu1_BUILDING.txt.gz

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

Title:
  FTBFS: tests fail on s390x due to incorrect regexp on /proc/cpuinfo

Status in git package in Ubuntu:
  In Progress

Bug description:
  git commit 29fb2ec384a867ca577335a12f4b45c184e7b642, present in 2.38.0
  and later, introduced a function that gets the number of cores from
  /proc/cpuinfo. It essentially does this:

      do { local @ARGV='/proc/cpuinfo'; return
  scalar(grep(/^processor\s*:/, <>)); } if -r '/proc/cpuinfo';

  On s390x, the ^processor lines are like this:

  processor 0: version = FF,  identification = 148F67,  machine = 2964

  In other arches (I checked amd64, armhf and arm64), they are like this
  instead:

  processor       : 0

  As a result, that function is returning 0 on s390x, and that value is
  used for the number of jobs the script should execute. Since it's
  zero, it exits without doing anything, and that breaks the test and
  the build[3] on s390x.

  1. https://github.com/git/git/commit/29fb2ec384a867ca577335a12f4b45c184e7b642
  2. https://github.com/git/git/commit/29fb2ec384a867ca577335a12f4b45c184e7b642#diff-e7042d714d4be11a06d153e6f2daeb3c3a9766b972522baab8ba113b962086cfR574
  3. https://launchpadlibrarian.net/635348769/buildlog_ubuntu-lunar-s390x.git_1%3A2.38.1-1ubuntu1_BUILDING.txt.gz

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




More information about the foundations-bugs mailing list