From: Carlos Maniero <carlos@maniero.me>
To: ~johnnyrichard/olang-devel@lists.sr.ht
Cc: Carlos Maniero <carlos@maniero.me>
Subject: [PATCH olang v2 0/3] test: cli: cover compilation pipeline
Date: Fri, 8 Mar 2024 19:39:06 -0300 [thread overview]
Message-ID: <20240308223909.3184226-1-carlos@maniero.me> (raw)
This patch is focused in coverig the entire compilation pipeline.
Although as it is the second integration test of the olang codebase it
also has a few housekeeping in order to provide a smooth test
experience.
V2:
- Add a comment to stop truncating the stdout
- Rename fd_pipe variable
Carlos Maniero (3):
tests: fix: rename dump tokens test name
tests: decouple command execution from cli_runner
tests: add tests for the minimal possible olang program
tests/integration/Makefile | 4 +--
tests/integration/cli_runner.c | 60 +++++++++++++-------------------
tests/integration/cli_runner.h | 10 ++++--
tests/integration/cli_test.c | 33 +++++++++++++++---
tests/integration/proc_exec.c | 63 ++++++++++++++++++++++++++++++++++
tests/integration/proc_exec.h | 36 +++++++++++++++++++
6 files changed, 159 insertions(+), 47 deletions(-)
create mode 100644 tests/integration/proc_exec.c
create mode 100644 tests/integration/proc_exec.h
--
2.34.1
next reply other threads:[~2024-03-08 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 22:39 Carlos Maniero [this message]
2024-03-08 22:39 ` [PATCH olang v2 1/3] tests: fix: rename dump tokens test name Carlos Maniero
2024-03-08 22:39 ` [PATCH olang v2 2/3] tests: decouple command execution from cli_runner Carlos Maniero
2024-03-08 22:39 ` [PATCH olang v2 3/3] tests: add tests for the minimal possible olang program Carlos Maniero
2024-03-08 22:40 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-03-08 23:59 ` [PATCH olang v2 0/3] test: cli: cover compilation pipeline Johnny Richard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240308223909.3184226-1-carlos@maniero.me \
--to=carlos@maniero.me \
--cc=~johnnyrichard/olang-devel@lists.sr.ht \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.johnnyrichard.com/olang.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox