Design Tools And Laboratory Engineering (2026): Exam#

Scenario#

You are called to work with a team on the project linked above. People expect you to become acquainted with it before you start working - clone its source code, build it, test it, and run the firmware that is built.

While you are doing your job, you notice that the project’s tests don’t pass. The project appears to be in a somewhat rotten state - somebody has committed and published code that does not pass its own tests. It turns out that that somebody has left the team just after the commit, and it’s you who is going to take over.

Conventions#

The project’s README (you can see it nicely rendered on the project’s Github page when you scroll down a bit) explains thoroughly how the project is built and tested. What is missing though is the exact location of the artifacts; it only says <SRCDIR> and <BUILDDIR>.

To fill that gap, the team has come up with unwritten conventions:

<SRCDIR> is $HOME/DTLE-2026. This means that git clone from your home directory, thereby creating a subdirectory DTLE-2026 in that directory.

$ cd ~             # if not at home already
$ git clone https://github.com/jfasch/DTLE-2026.git
$ ls -l
...
drwxr-xr-x. 1 jfasch jfasch  236 Sep 29 19:46 DTLE-2026
...

<BUILDDIR> is $HOME/DTLE-2026-build. You create that directory by saying
```
$ mkdir ~/DTLE-2026-build
```

Your Mission#

Clone the project, respecting the conventions (source is in $HOME/DTLE-2026)
Create a build directory, respecting the conventions (build is in $HOME/DTLE-2026-build)
Build the project
Fix the failing test

Pack the modifications that you made

$ cd ~              # ensure that you are at home
$ tar --exclude .git -zcf submission.tar.gz DTLE-2026

This creates a file submission.tar.gz in your home directory.

Submit submission back to where you started