nushell/scripts
Filip Andersson 3143ded374
Tango migration (#12469)
# Description

This PR migrates the benchmark suit to Tango. Its different compared to
other framework because it require 2 binaries, to run to do A/B
benchmarking, this is currently limited to Linux, Max, (Windows require
rustc nightly flag), by switching between two suits it can reduce noise
and run the code "almost" concurrently. I have have been in contact with
the maintainer, and bases this on the dev branch, as it had a newer API
simular to criterion. This framework compared to Divan also have a
simple file dump system if we want to generate graphs, do other analysis
on later. I think overall this crate is very nice, a lot faster to
compile and run then criterion, that's for sure.
2024-05-05 15:53:48 +00:00
..
build-all-maclin.sh Remove feat extra and include in default (#12140) 2024-03-10 17:29:02 +01:00
build-all-windows.cmd Remove feat extra and include in default (#12140) 2024-03-10 17:29:02 +01:00
build-all.nu Remove feat extra and include in default (#12140) 2024-03-10 17:29:02 +01:00
build.rs Tango migration (#12469) 2024-05-05 15:53:48 +00:00
coverage-local.nu Add long options for path (#10775) 2023-10-19 22:07:01 +02:00
coverage-local.sh Fix unit tests on Android (#10224) 2023-09-05 20:17:34 +12:00
install-all.ps1 Remove feat extra and include in default (#12140) 2024-03-10 17:29:02 +01:00
install-all.sh Remove feat extra and include in default (#12140) 2024-03-10 17:29:02 +01:00
README.md REFACTOR: clean the root of the repo (#9231) 2023-05-20 07:57:51 -05:00
register-plugins.nu add a new toolkit install command with --features support (#9288) 2023-05-26 11:22:34 +02:00
test_virtualenv.nu Check for clean repo after tests (#11409) 2023-12-23 20:28:07 +01:00
uninstall-all.sh update install/build scripts to include --locked (#10086) 2023-08-21 12:42:42 -05:00

run the scripts

Note


the following table must be read as follows:

  • an x means it works
  • a ? means no data available

.nu scripts must be run as nu .../foo.nu
.sh scripts must be run as ./.../foo.sh
.ps1 scripts must be run as powershell .../foo.ps1

let's say a script is called foo

  • an x in the ./scripts column means foo can be run from ./scripts
  • an x in the root column means foo can be run from the root of nushell
  • an x in the anywhere column means foo can be run from anywhere!
script ./scripts/ root anywhere
build-all-maclin.sh x x x
build-all-windows.cmd ? x ?
build-all.nu x x x
coverage-local.nu x x x
coverage-local.sh x x x
install-all.ps1 ? x ?
install-all.sh x x x
register-plugins.nu x x x
uninstall-all.sh x x x