Garmelon/tablejohn
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Velcom 2.0 written in Rust
123 commits 1 branch 0 tags 656 KiB
Find a file
Joscha 5c8c037417 Move logo inside first nav <a>
2023-08-10 17:50:23 +02:00
.sqlx Identify queue items by commit hash, not id 2023-08-09 16:20:20 +02:00
.vscode Fix VSCode config and dev instructions 2023-08-05 23:01:29 +02:00
meta Update and document scripts 2023-08-05 19:42:59 +02:00
migrations Create tables for runs and measurements 2023-08-09 16:27:25 +02:00
scripts/queue Fix build script not using $OUT_PATH 2023-08-07 02:21:32 +02:00
src Add web.runner_token and web.runner_timeout options 2023-08-10 17:50:23 +02:00
static Move logo inside first nav <a> 2023-08-10 17:50:23 +02:00
templates Move logo inside first nav <a> 2023-08-10 17:50:23 +02:00
.env Fix project not compiling without dev.db 2023-08-05 16:20:32 +02:00
.gitignore Create project 2023-08-03 14:32:37 +02:00
askama.toml Use askama to render test template 2023-08-03 19:14:58 +02:00
build.rs Fix build script not using $OUT_PATH 2023-08-07 02:21:32 +02:00
Cargo.lock Model server-runner communication 2023-08-10 17:50:23 +02:00
Cargo.toml Model server-runner communication 2023-08-10 17:50:23 +02:00
DESIGN.md Update design notes on runner api 2023-08-10 17:50:23 +02:00
README.md Write down more design notes 2023-08-08 02:43:24 +02:00
tsconfig.json Fix build script not using $OUT_PATH 2023-08-07 02:21:32 +02:00

README.md

tablejohn

Run benchmarks against commits in a git repo and present their results.

Building from source

The following tools are required:

Once you have installed these tools, run the following command to install or update tablejohn to ~/.cargo/bin/tablejohn:

cargo install --force --git https://github.com/Garmelon/tablejohn

Alternatively, clone the repo and run cargo build --release. The compiled binary will be located at target/release/tablejohn.

The binary produced by either of these steps contains everything needed to run tablejohn. Not additional files are required.

Developing

I recommend using VSCode and rust-analyzer in combination with the tools mentioned in the previous section. However, some parts of the code base require additional tools and setup.

Changing SQL queries with sqlx

If you want to change any of the SQL queries, you will need to install sqlx, the CLI of the sqlx library. The sqlx library can connect to a dev database at compile-time to verify SQL queries defined via the query* macro family. This is useful during development as it gives immediate feedback on mistakes in your queries. However, it requires a bit of setup. During normal compilation with cargo build, the cached query analyses in .sqlite/ are used instead of the dev database. This way, the dev database and sqlx tool is not required when you're just building the project.

First, run ./meta/setup. This creates or updates the dev database at target/dev.db. You will need to rerun this command whenever you change or add a migration.

Then, if you don't use VSCode, configure your rust-analyzer to run with the with the environment variable SQLX_OFFLINE=false using the rust-analyzer.server.extraEnv option. This signals to sqlx that it should use the dev database instead of .sqlx/, but only in your IDE.

Important: Before committing any changed SQL query, you must run ./meta/update_sqlx_queries. This will recreate your dev database (just like ./meta/setup) and then update the files in .sqlx/.