Update rotate.c

2 jobs for master in 5 seconds (queued for 5 seconds)

Status	Job ID	Name
Check
failed	#26302	linter	00:00:05 3 years ago

Test
skipped	#26303	test

Name Stage Failure

	Name	Stage	Failure
failed	linter	Check
	`/builds/pyrani/assignment-image-rotation/solution/src/rotate.c:1:1: error: #includes are not sorted properly [llvm-include-order,-warnings-as-errors] #include <stdlib.h> ^ ~~~~~~~~~~ <stdint.h> Suppressed 14 warnings (14 in non-user code). Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well. 5 warnings treated as errors Cleaning up file based variables ERROR: Job failed: exit code 1`

failed

linter

Check

/builds/pyrani/assignment-image-rotation/solution/src/rotate.c:1:1: error: #includes are not sorted properly [llvm-include-order,-warnings-as-errors]
#include <stdlib.h>
^        ~~~~~~~~~~
         <stdint.h>
Suppressed 14 warnings (14 in non-user code).
Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
5 warnings treated as errors
Cleaning up file based variables
ERROR: Job failed: exit code 1

Speed up your pipelines with Needs relationships

Using the needs keyword makes jobs run before their stage is reached. Jobs run as soon as their needs relationships are met, which speeds up your pipelines.

If you add needs to jobs in your pipeline you'll be able to view the needs relationships between jobs in this tab as a Directed Acyclic Graph (DAG).

Learn more about Needs relationships