The goal of the Fedora CI is to run "basic functionality" and "integration" tests. Avocado's gdbtest.py does both, as it exercises the Avocado test and utils APIs, and also communicates with GDB, thus ensuring some integration validation with those packages. Reference: https://fedoraproject.org/wiki/CI Signed-off-by: Cleber Rosa <crosa@redhat.com>
47 lines
589 B
C
47 lines
589 B
C
#include <stdio.h>
|
|
#include <stdlib.h>
|
|
|
|
void empty()
|
|
{
|
|
}
|
|
|
|
void write_stdout()
|
|
{
|
|
fprintf(stdout, "testing output to stdout\n");
|
|
}
|
|
|
|
void write_stderr()
|
|
{
|
|
fprintf(stderr, "testing output to stderr\n");
|
|
}
|
|
|
|
int forkme()
|
|
{
|
|
int pid;
|
|
|
|
pid = fork();
|
|
if (pid != 0)
|
|
pid = fork();
|
|
if (pid != 0)
|
|
pid = fork();
|
|
|
|
return pid;
|
|
}
|
|
|
|
int main(int argc, char *argv[])
|
|
{
|
|
int exit_status = 99;
|
|
|
|
if (argc > 1)
|
|
exit_status = atoi(argv[1]);
|
|
|
|
empty();
|
|
write_stdout();
|
|
write_stderr();
|
|
|
|
if (forkme()) {
|
|
fprintf(stdout, "return %i\n", exit_status);
|
|
}
|
|
|
|
return exit_status;
|
|
}
|