[LU-6224] e2fsprogs build for ppc64 fails in 'make check' Created: 09/Feb/15  Updated: 09/Feb/15  Resolved: 09/Feb/15

Status: Closed
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Frank Heckes (Inactive) Assignee: WC Triage
Resolution: Not a Bug Votes: 0
Labels: None

Attachments: File build-e2fsprogs.sh     Text File e2fsprogs-build-2015-02-08-6.log     Text File e2fsprogs-build-2015-02-09-1.log    
Issue Links:
Related
Severity: 3
Rank (Obsolete): 17419

 Description   
  • Local build (not using Jenkins) for e2fsprogs on ppc64 (shadow-32) failed in section 'make j16 check' for tests f_dirdata f_eofblocks f_pgsize_gt_blksize s_basic_scan. See also attached build log file 'e2fsprogs-build-2015-02-08-6.log'. Therefore no build artifacts (RPMs) are created.
  • Build procedure used (same as for Jenkins besides executed manually)
    • git clone
    • git checkout master-lustre
    • Execute Jenkins wrapper 'build-e2fsprogs.sh' (see attached file)
      node
  • In principle the e2fsprogs RPMs can be created successful (see attached build log file 'e2fsprogs-build-2015-02-09-1.log') in case the 'checks' are disabled using the following procedure:
    • Clean the repo:
      git reset --hard
      git clean -dfx
      
    • Comment out 'make check' section in the autoconf templated SPEC file e2fsprogs-RHEL-6.spec.in (line 190)
    • Comment out git reset, git clean commands in build script build-e2fsprogs.sh (lines 72, 73)
    • Execute build-e2fsprogs.sh in toplevel directory of e2fsprogs GIT
      NOTE: local build has been utiliised to avoid negative impact on the production pipe.


 Comments   
Comment by Frank Heckes (Inactive) [ 09/Feb/15 ]

Log file containing info about failed build

Comment by Frank Heckes (Inactive) [ 09/Feb/15 ]

'Jenkins' wrapper script used to steer the e2fsprog build

Comment by Frank Heckes (Inactive) [ 09/Feb/15 ]

Log file containing info about successful build in case 'make check' is switch off in e2fsprogs-RHEL-6.spec file

Comment by Andreas Dilger [ 09/Feb/15 ]

The e2fsprogs packages are only needed on the server, except for some limited testing of filefrag/FIEMAP on the client (which I think is skipped if it is unavailable).

Are you currently working on getting Lustre servers functional on PPC? I think it would be better to start by having only the client PPC testing working, and then we can work on getting PPC servers afterward. Most users (e.g. LLNL and other BlueGene systems only need client-side PPC support).

Comment by Frank Heckes (Inactive) [ 09/Feb/15 ]

No, I'm not working on server support, actually on client support as you described. The problem occurred due to a missing query in kickstart file. I was confused by the error message that e2fsprogs should be installed and was missing. Many thanks for clarification and sorry for creating the spam.

Generated at Sat Feb 10 01:58:21 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.