aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/src/process.c (follow)
Commit message (Collapse)AuthorAge
* switch to egor@tensin.nameEgor Tensin2023-12-12
|
* process: portable exit code processingEgor Tensin2023-07-26
|
* process: preserve the exit code moreEgor Tensin2023-07-18
| | | | | If the process is killed by a signal, preserve the exit code as it would be reported by $?.
* store process output in SQLiteEgor Tensin2023-07-09
|
* use __WNOTHREAD w/ waitpidEgor Tensin2023-06-30
| | | | | | | | | | I learned about this flag on my previous job; basically, it should be enabled by default IMO, so that the thread doesn't receive signals from other threads' children. Here, it doesn't matter too much, since we're waiting for a specific child. However, if we were to use waitpid(-1, ...), it would be essential to use this flag. Still, even here, it's good to have this on.
* process: fix function name in logsEgor Tensin2023-06-28
|
* minor refactoringEgor Tensin2023-06-14
|
* add {file,net}_close as a wrapper to close(2)Egor Tensin2023-06-09
|
* process: add process_output_dumpEgor Tensin2023-05-14
|
* add copyright noticesEgor Tensin2022-12-02
|
* log: refactoringEgor Tensin2022-09-08
|
* ci: set some environment variablesEgor Tensin2022-09-07
|
* worker: fix a crashEgor Tensin2022-08-28
| | | | Found when running in Docker.
* holy crap, it actually kinda works nowEgor Tensin2022-08-28
| | | | | | | | | | | | | | | | | | | | | | | Previously, I had a stupid system where I would create a thread after every accept(), and put worker descriptors in a queue. A special "scheduler" thread would then pick them out, and give out jobs to complete. The problem was, of course, I couldn't conveniently poll job status from workers. I thought about using poll(), but that turned out to be a horribly complicated API. How do I deal with partial reads, for example? I don't honestly know. Then it hit me that I could just use the threads that handle accept()ed connections as "worker threads", which would synchronously schedule jobs and wait for them to complete. This solves every problem and removes the need for a lot of inter-thread synchronization magic. It even works now, holy crap! You can launch and terminate workers at will, and they will pick up new jobs automatically. As a side not, msg_recv_and_handle turned out to be too limiting and complicated for me, so I got rid of that, and do normal msg_recv/msg_send calls.
* add check_errno macroEgor Tensin2022-08-26
|
* worker: capture process outputEgor Tensin2022-08-26
|
* add some more codeEgor Tensin2022-08-26
This adds a basic "worker" program. You can now do something like ./server & ./worker & ./client ci_run URL REV and the server should pass a message to worker, after which it should clone the repository at URL, checkout REV, and try to run the CI script. It's extremely unfinished: I need to sort out the graceful shutdown, how the server manages workers, etc.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 16:57:54 +0000