Every exercise in this book

Every exercise is on the page that just taught the object it tests.

Each page includes one or two items, positioned where the page has just taught the concept they test. This page enumerates all items in reading order. A taught session may select a subset, and an individual reader can locate the desired item. Each item possesses an id that remains stable across edits. The stable id can be referenced aloud, in messages, or in shared documents during a workshop.

An easyconfig is Python

• EB-Python-1: Read a class name backwards

• EB-Python-2: The smallest change that fixes it

• EB-Python-fade-1: Fill the hole the linter names

A toolchain is a hierarchy

• EB-Toolchain-1: What may this package depend on

A pin is for one generation

• EB-Pin-1: Two numbers, two different claims

• EB-Pin-mcq-1: What the second field claims

The robot

• EB-Robot-1: Where do the defaults go

• EB-Robot-2: The same command, two different plans

A versionsuffix is part of the name

• EB-Suffix-1: Are these the same toolchain

What “installed” means

• EB-Installed-1: What has this green build established

A checksum is a claim about bytes

• EB-Checksum-1: One architecture, one missing key

One easyconfig, many installs

• EB-Extensions-1: Which name is this

A hook changes a file you are not reading

• EB-Hook-1: The commands that never ran

Build your own, without asking anyone

• EB-Own-1: It built, and it will not load

EESSI, somebody else’s stack

• EB-EESSI-1: The 2025.06 tree does not carry 2026.1

eb-stack ports a recipe and bumps one

• EB-Port-1: Port, bump, or neither

How a build executes

• EB-Steps-1: Which step, and which parameter

• EB-Steps-parsons-1: Put the first six in order

The isolation policy

• EB-Isolation-1: Works for me, fails for the desk

Build dependencies are not dependencies

• EB-Builddeps-1: Which list, and how to check

What a toolchain injects

• EB-Toolchainopts-1: Four errors, four options

Patches, and what a patch is relative to

• EB-Patches-1: It still applies, and it is still wrong

Languages that bring their own package manager

• EB-Languages-1: Three requests, three answers

What a module exports

• EB-Module-1: Where did that line come from

Reading a failed build

• EB-Failure-1: Four failures, four first moves

• EB-Failure-2: Read this log fragment

Writing one from nothing

• EB-Write-1: From a tarball and a README

• EB-Write-2: Read a checksums block

Writing an easyblock

• EB-Easyblock-1: Four requests, and only one of them is code

Testing, and the four things it can mean

• EB-Testing-1: Four reports, four responses

Standing where the build stood

• EB-DevEnv-1: Four people who need an environment

• EB-DevEnv-2: Archaeology on one install

Reading a stack off the wire: CernVM-FS

• EB-CVMFS-1: Six symptoms, six layers

• EB-CVMFS-2: Verify a repository yourself

• EB-CVMFS-3: Where would that number come from

The same stack somewhere else

• EB-Elsewhere-1: Four machines

• EB-Elsewhere-2: Which target did you get

Four things that actually happened

• EB-History-1: Which of the four is this

Your first week on somebody’s stack

• EB-Week-1: Your actual first ticket

• EB-Week-2: The commit you would write

Extensions, and what an entry in exts_list inherits

• EB-Exts-1: Four entries, four outcomes

An easystack is the list the bot will build

• EB-Easystack-1: Which file, and which options

• EB-Easystack-2: What the bot will type

The bot is three processes and a comment

• EB-Bot-1: What this comment starts

• EB-Bot-2: Order the pipeline

A site stack next to EESSI, not inside it

• EB-Site-1: Which prefix, which variable

• EB-Site-2: 2023.06 or 2025.06

Inspect writes a work queue, not a recipe

• EB-Plan-1: What is missing from this command

• EB-Residual-1: Note, residual, or claim

Format, lint and check are three different questions

• EB-Recipe-1: Which command

A stack lock is not a package lock

• EB-Stack-1: Which file answers

A campaign finding is a typed failure, not a log

• EB-Campaign-1: Class this failure

A wrapper is the range EasyBuild will not write

• EB-Dry-1: What -D prints

• EB-Wrap-1: Pin, wrap, or rebuild

Four EasyBuild 5 surfaces the earlier pages skipped

• EB-Five-1: Which lock, which prefix

A ReFrame test is a class

• EB-ReFrame-39-1: What decides a pass

The pipeline has six stages

• EB-ReFrame-40-1: Name the failing stage

The configuration file is the machine

• EB-ReFrame-41-1: What belongs where

A performance function is a number with a unit

• EB-ReFrame-42-1: Sanity or performance

Compile or run-only

• EB-ReFrame-43-1: Which base class

Parameters multiply the suite

• EB-ReFrame-44-1: Count the cases

A portable test leaves the machine in the config

• EB-ReFrame-45-1: What to move

Software maps to tests

• EB-ReFrame-46-1: Which filter

Reading a failed ReFrame run

• EB-ReFrame-47-1: Where to look

SeisSol, from a Spack recipe to a PR

• EB-SeisSol-1: Inspect, bump, or plan

• EB-SeisSol-2: Which claim failed

The catalog names every exercise by id, including ``EB-Pin-mcq-1``, ``EB-Robot-1``, ``EB-Python-1``, ``EB-Bot-1``.

The catalog

• An easyconfig is Python

  • EB-Python-1: Read a class name backwards

  • EB-Python-fade-1: Fill the hole the linter names

  • EB-Python-2: The smallest change that fixes it

• A toolchain is a hierarchy

  • EB-Toolchain-1: What may this package depend on

• A pin is for one generation

  • EB-Pin-mcq-1: What the second field claims

  • EB-Pin-1: Two numbers, two different claims

• The robot

  • EB-Robot-1: Where do the defaults go

  • EB-Robot-2: The same command, two different plans

• A versionsuffix is part of the name

  • EB-Suffix-1: Are these the same toolchain

• What “installed” means

  • EB-Installed-1: What has this green build established

• A checksum is a claim about bytes

  • EB-Checksum-1: One architecture, one missing key

• One easyconfig, many installs

  • EB-Extensions-1: Which name is this

• A hook changes a file you are not reading

  • EB-Hook-1: The commands that never ran

• Build your own, without asking anyone

  • EB-Own-1: It built, and it will not load

• EESSI, somebody else’s stack

  • EB-EESSI-1: Every dependency says SKIPPED

• eb-stack ports a recipe and bumps one

  • EB-Port-1: Port, bump, or neither

• How a build executes

  • EB-Steps-parsons-1: Put the first six in order

  • EB-Steps-1: Which step, and which parameter

• The isolation policy

  • EB-Isolation-1: Works for me, fails for the desk

• Build dependencies are not dependencies

  • EB-Builddeps-1: Which list, and how to check

• What a toolchain injects

  • EB-Toolchainopts-1: Four errors, four options

• Patches, and what a patch is relative to

  • EB-Patches-1: It still applies, and it is still wrong

• Languages that bring their own package manager

  • EB-Languages-1: Three requests, three answers

• What a module exports

  • EB-Module-1: Where did that line come from

• Reading a failed build

  • EB-Failure-2: Read this log fragment

  • EB-Failure-1: Four failures, four first moves

• Writing one from nothing

  • EB-Write-2: Read a checksums block

  • EB-Write-1: From a tarball and a README

• Writing an easyblock

  • EB-Easyblock-1: Four requests, and only one of them is code

• Testing, and the four things it can mean

  • EB-Testing-1: Four reports, four responses

• Standing where the build stood

  • EB-DevEnv-2: Archaeology on one install

  • EB-DevEnv-1: Four people who need an environment

• Reading a stack off the wire: CernVM-FS

  • EB-CVMFS-2: Verify a repository yourself

  • EB-CVMFS-3: Where would that number come from

  • EB-CVMFS-1: Six symptoms, six layers

• The same stack somewhere else

  • EB-Elsewhere-2: Which target did you get

  • EB-Elsewhere-1: Four machines

• Four things that actually happened

  • EB-History-1: Which of the four is this

• Your first week on somebody’s stack

  • EB-Week-2: The commit you would write

  • EB-Week-1: Your actual first ticket

• Extensions, and what an entry in exts_list inherits

  • EB-Exts-1: Four entries, four outcomes

• An easystack is the list the bot will build

  • EB-Easystack-1: Which file, and which options

  • EB-Easystack-2: What the bot will type

• The bot is three processes and a comment

  • EB-Bot-1: What this comment starts

  • EB-Bot-2: Order the pipeline

• A site stack next to EESSI, not inside it

  • EB-Site-1: Which prefix, which variable

  • EB-Site-2: 2023.06 or 2025.06

• Inspect writes a work queue, not a recipe

  • EB-Residual-1: Note, residual, or claim

  • EB-Plan-1: What is missing from this command

• Format, lint and check are three different questions

  • EB-Recipe-1: Which command

• A stack lock is not a package lock

  • EB-Stack-1: Which file answers

• A campaign finding is a typed failure, not a log

  • EB-Campaign-1: Class this failure

• A wrapper is the range EasyBuild will not write

  • EB-Wrap-1: Pin, wrap, or rebuild

  • EB-Dry-1: What -D prints

• Four EasyBuild 5 surfaces the earlier pages skipped

  • EB-Five-1: Which lock, which prefix

• A ReFrame test is a class

  • EB-ReFrame-39-1: What decides a pass

• The pipeline has six stages

  • EB-ReFrame-40-1: Name the failing stage

• The configuration file is the machine

  • EB-ReFrame-41-1: What belongs where

• A performance function is a number with a unit

  • EB-ReFrame-42-1: Sanity or performance

• Compile or run-only

  • EB-ReFrame-43-1: Which base class

• Parameters multiply the suite

  • EB-ReFrame-44-1: Count the cases

• A portable test leaves the machine in the config

  • EB-ReFrame-45-1: What to move

• Software maps to tests

  • EB-ReFrame-46-1: Which filter

• Reading a failed ReFrame run

  • EB-ReFrame-47-1: Where to look

• SeisSol, from a Spack recipe to a PR

  • EB-SeisSol-1: Inspect, bump, or plan

  • EB-SeisSol-2: Which claim failed