Running with gitlab-runner 16.6.1 (f5da3c5a)
  on sw-gitlab-runner-02.grid.pub.ro 7cgfvYtj, system ID: s_00faffb20f26
section_start:1712599245:prepare_executor
Preparing the "docker" executor
Using Docker executor with image gitlab.cs.pub.ro:5050/so2/2-uart ...
Starting service docker:19.03.12-dind ...
Pulling docker image docker:19.03.12-dind ...
Using docker image sha256:66dc2d45749a48592f4348fb3d567bdd65c9dbd5402a413b6d169619e32f6bd2 for docker:19.03.12-dind with digest docker@sha256:674f1f40ff7c8ac14f5d8b6b28d8fb1f182647ff75304d018003f1e21a0d8771 ...
Waiting for services to be up and running (timeout 30 seconds)...

*** WARNING: Service runner-7cgfvytj-project-5987-concurrent-0-cef32fe98f1e9f7b-docker-0 probably didn't start properly.

Health check error:
start service container: Error response from daemon: Cannot link to a non running container: /runner-7cgfvytj-project-5987-concurrent-0-cef32fe98f1e9f7b-docker-0 AS /runner-7cgfvytj-project-5987-concurrent-0-cef32fe98f1e9f7b-docker-0-wait-for-service/service (services.go:198:0s)

Service container logs:
2024-04-08T18:00:52.182120564Z mount: permission denied (are you root?)
2024-04-08T18:00:52.182195876Z Could not mount /sys/kernel/security.
2024-04-08T18:00:52.182222929Z AppArmor detection and --privileged mode might break.
2024-04-08T18:00:52.183182627Z mount: permission denied (are you root?)

*********

Authenticating with credentials from job payload (GitLab Registry)
Pulling docker image gitlab.cs.pub.ro:5050/so2/2-uart ...
Using docker image sha256:47745e2cf31cb376fd48da39f232b1ffb743b9f91dd76bede567e7fce7ea46cc for gitlab.cs.pub.ro:5050/so2/2-uart with digest gitlab.cs.pub.ro:5050/so2/2-uart@sha256:83f990b34d9df880b46dab7d918abfb525ade5926cdde8983e8483d9d186faef ...
section_end:1712599263:prepare_executor
section_start:1712599263:prepare_script
Preparing environment
Running on runner-7cgfvytj-project-5987-concurrent-0 via sw-gitlab-runner-02.grid.pub.ro...
section_end:1712599264:prepare_script
section_start:1712599264:get_sources
Getting source from Git repository
Fetching changes with git depth set to 20...
Initialized empty Git repository in /builds/so2/2-uart/.git/
Created fresh repository.
Checking out 08e8f12e as detached HEAD (ref is master)...

Skipping Git submodules setup
section_end:1712599267:get_sources
section_start:1712599267:step_script
Executing "step_script" stage of the job script
Using docker image sha256:47745e2cf31cb376fd48da39f232b1ffb743b9f91dd76bede567e7fce7ea46cc for gitlab.cs.pub.ro:5050/so2/2-uart with digest gitlab.cs.pub.ro:5050/so2/2-uart@sha256:83f990b34d9df880b46dab7d918abfb525ade5926cdde8983e8483d9d186faef ...
$ ./checker/checker.sh $ASSIGNMENT
Copying the contents of src/ into /linux/tools/labs/skels/assignments/2-uart
Copying the contents of checker/2-uart-checker into /linux/tools/labs/skels/assignments/2-uart-checker
Checking if uart16550.ko exists before build
Cleaning /linux/tools/labs/skels/assignments/2-uart => Will remove: *.o *.mod *.mod.c .*.cmd *.ko modules.order
Overwrite from /linux/tools/labs/templates/assignments/2-uart/uart16550.h
Building...
echo "# autogenerated, do not edit " > skels/Kbuild
echo "ccflags-y += -Wno-unused-function -Wno-unused-label -Wno-unused-variable " >> skels/Kbuild
for i in ; do echo "obj-m += $i/" >> skels/Kbuild; done
make -C /linux M=/linux/tools/labs/skels ARCH=x86 modules
make[1]: Entering directory '/linux'
  MODPOST /linux/tools/labs/skels/Module.symvers
make[1]: Leaving directory '/linux'
for i in skels/assignments/2-uart-checker; do make -C $i; done
make[1]: Entering directory '/linux/tools/labs/skels/assignments/2-uart-checker'
cc -Wall -g -static -m32   -c -o _test/test.o _test/test.c
cc -Wall -g -static -m32 -o test _test/test.o
ln -s _test/solution.ko solution.ko
make[1]: Leaving directory '/linux/tools/labs/skels/assignments/2-uart-checker'
<VMCK_NEXT_BEGIN>
Cannot find uart16550.ko
	-Make sure you have the sources directly in the root of the archive.
	-Make sure you have not changed the header that comes with the code skeleton.
	-Make sure the assignment compiles in a similar environment as vmchecker-next by running './local.sh checker <assignment-name>'.
After you have solved the problems, resubmit the assignment on moodle until the score appears as feedback, otherwise, the assignment will not be graded.
<VMCK_NEXT_END>
section_end:1712599270:step_script
section_start:1712599270:cleanup_file_variables
Cleaning up project directory and file based variables
section_end:1712599273:cleanup_file_variables
Job succeeded