What EasyBuild Is Doing
  • Journeys
  • The recipe
  • The stack
  • The test
/
  • Journeys
  • Journey: first recipe
  • Journey: a build failed
  • Journey: port a package
  • Journey: write a test
  • The recipe
    • Read a file
      • Tutorial: read an easyconfig the way EasyBuild does
      • Playground
      • An easyconfig is Python
      • A toolchain is a hierarchy
      • A pin is for one generation
      • The robot
    • When it fails
      • A versionsuffix is part of the name
      • What “installed” means
      • A checksum is a claim about bytes
      • One easyconfig, many installs
      • A hook changes a file you are not reading
      • Reading a failed build
      • Four things that actually happened
      • Your first week on somebody’s stack
    • How it runs
      • How a build executes
      • What a build is allowed to see
      • Build dependencies are not dependencies
      • What a toolchain injects
      • Patches, and what a patch is relative to
      • Languages that bring their own package manager
      • What a module exports
      • Standing where the build stood
    • Write one
      • Build your own, without asking anyone
      • eb-stack ports a recipe and bumps one
      • Writing one from nothing
      • Writing an easyblock
      • Extensions, and what an entry in exts_list inherits
      • Inspect writes a work queue, not a recipe
      • Format, lint, and check are three different questions
      • A stack lock is not a package lock
      • A campaign finding is a typed failure, not a log
      • A wrapper is the range EasyBuild will not write
      • Four EasyBuild 5 surfaces the earlier chapters skipped
  • The stack
    • EESSI, somebody else’s stack
    • Reading a stack off the wire: CernVM-FS
    • The same stack somewhere else
    • An easystack is the list the bot will build
    • The bot is three processes and a comment
    • A site stack next to EESSI, not inside it
  • The test
    • Testing, and the four things it can mean
    • A ReFrame test is a class
    • The pipeline has six stages
    • The configuration file is the machine
    • A performance function is a number with a unit
    • Compile or run-only
    • Parameters multiply the suite
    • A portable test leaves the machine in the config
    • Software maps to tests
    • Reading a failed ReFrame run
  • A path through this book
  • Glossary
  • What to remember
  • Every exercise in this book
  • References
  • At the back
  • Afterword: when EasyBuild is the wrong tool
  1. What EasyBuild Is Doing /
  2. Journey: a build failed

Journey: a build failed¶

The log first. Then the parameters that usually caused it.

  1. Reading a failed build

  2. A versionsuffix is part of the name

  3. What “installed” means

  4. A checksum is a claim about bytes

  5. A hook changes a file you are not reading

Previous
Journey: first recipe
Next
Journey: port a package

2026, Rohit Goswami

Made with Sphinx and Shibuya theme.