ALR-TEST(1)

📦
version 1.2.1 · 2 versions
, in debian trixie, ubuntu questing, ubuntu resolute, ubuntu stonking

💖 ALR-TEST(1) — the Alire manual, bestie edition 💖

okay so. this is alr-test, page 1 of the Alire manual, and it's literally the tool that tests whether every release out there can be fetched and built. imagine being that responsible. icon behaviour. 🎀

✨ NAME ✨

alr-test — tests the compilation of all or some releases 🦋

🌸 SYNOPSIS 🌸

alr test [options] [crate[versions]]...

💅 OPTIONS 💅

  • --continue — skips the releases that are already sitting in the folder. no need to redo the ones you've done, we're not doing busywork 💖
  • --docker[=IMAGE] — tests the releases inside a docker IMAGE (or alire/gnat:debian-stable if you don't hand it one). containerised slay ✨
  • --full — tests all indexed crates. every single one. the whole roster 👑
  • --newest — tests only the newest release in each crate. fresh out the box 🌸
  • --redo — retests the releases already in the folder (and yeah, this implies --continue). second chances fr fr 💜
  • --search — treats your arguments as substrings instead of exact crate names. fuzzy matching, we love to see it 🔍

🌈 GLOBAL OPTIONS 🌈

  • -c, --config=ARG — overrides the configuration folder location 📁
  • -f, --force — keeps going even after a recoverable troublesome situation. we push through 💪
  • -h, --help — shows general help, or help specific to a command 🙋
  • -n, --non-interactive — assumes the default answer for every single prompt. no questions, just vibes 🧚
  • --no-color — disables colors in the output. monochrome era 🖤
  • --no-tty — disables control characters in the output
  • --prefer-oldest — prefers oldest versions instead of newest when resolving dependencies. vintage core 🕰️
  • --version — displays the version and exits, bye ✌️
  • -q — limits output to errors only. silent treatment, but productive 💀
  • -v — be more verbose (use it twice for extra detail). spill the tea ☕
  • -d, --debug[] — enables debug-specific log messages 🐛

🎀 DESCRIPTION 🎀

So basically: this tests the retrievability and buildability of all the releases, or just the specific ones you name. Unless you pass --continue or --redo, the command expects to be run in an empty folder. empty folder, clean slate, main character energy ✨

⚠️ no cap — if you run it in a folder that already has stuff in it and you didn't say --continue or --redo, that's not the vibe it's expecting.

Once it's done, a report in text, markup and junit format will be available in the current directory. and the complete log of each release's building process will be sitting in the respective <release>/alire/alr_test.log files. receipts for everything 🧾💖

Version selection syntax — the global policy applies within the allowed version subsets, iykyk:

  • crate — newest/oldest version
  • crate=version — exact version
  • crate^version — major-compatible version
  • crate~version — minor-compatible version

👑 SEE ALSO 👑

alr(1), alr-action(1), alr-build(1), alr-clean(1), alr-dev(1), alr-edit(1), alr-run(1), alr-exec(1), gprbuild(1)

the whole friend group, go say hi 🫶

🦋 AUTHOR 🦋

Generated with generate-man from Alire execution ⭐

and that's the page bestie!! 💜 this was Alire 1.2, dated Aug 3, 2022, and the header up top read ALR-TEST(1) under the Alire manual — go build something gorgeous, ily, bye 🎀✨💅

📦 where this page comes from