adam mccartney

Actually this is the default behavior assuming that we have just initialized a new repository. However, as soon as we commit something, the HEAD should be updated to point at...

Can you please make sure to document the proposed changes? We would like to build up a set of design documents for grader service in the `docs/` folder. They don't...

Reminder to consider #79 when looking at a solution for this

hi @milandeepbassi, Thanks for your request - we're in the middle of a fairly major upgrade at the moment, we're working through a release of version "0.2.*" for the `grader-service`,...

Ah cool, thanks for the detailed answer! I think my issue was not using the python from eessi's compat layer. Instead loaded the default python module, created the venv and...

Actually, I wanted to ask about the installed modules in the environment. This is really cool, how are you getting a base set of modules to appear in the venv?...

> Hi @adammccartney , > > As in the PR there is no build generate with its corresponding tests, could you kindly share the steps you did to test this...

So, interestingly the sanity check now fails if I try to build this directly on a compute node (`x86_64/amd/zen4` is the architecture by the way) . The initial build was...

bot: build inst:eessi-bot-mc-azure arch:x86_64/amd/zen4 repo:eessi.io-2023.06-software accelerator:nvidia/cc90

Okay, so I got this working with some careful attention to what the linker was up to. See the commit message https://github.com/EESSI/software-layer/pull/1043/commits/a2fe8bec8e70561e34e92273b696632fdb30f5d5 For a bit more info.