maelstrom-software/maelstrom

Issues

• Cargo workspaces with root packages can confuse `cargo-maelstrom`

  #427 opened 2 months ago by nfachan
  0

• Migrate off of GitHub artifacts v3 action.

  #426 opened 2 months ago by nfachan
  0

• Use ratatui v0.29.0

  #423 opened 2 months ago by nfachan
  0

• Provide a way to examine results, stdout, and stderr from previous tests runs

  #381 opened 5 months ago by nfachan
  0

• Change worker to not start a new thread for every artifact

  #425 opened 3 months ago by nfachan
  0

• Use slice/zero-copy for artifact pusher and artifact fetcher.

  #424 opened 3 months ago by nfachan
  0

• Cannot use maelstrom-pytest on Ubuntu 22.04

  #416 opened 4 months ago by nicolas-slamcore
  11

• Compilation warnings should be displayed after test runner complete

  #390 opened 5 months ago by nfachan
  4

• xtask distribute should be more automatic when generalizing binaries

  #419 opened 4 months ago by bobbobbio
  0

• UI somehow idicates if a job is being run locally or remotely

  #422 opened 4 months ago by bobbobbio
  0

• Fancy UI build progress window crops from the bottom

  #421 opened 4 months ago by bobbobbio
  0

• Fancy UI gauge has wiggle on the right side

  #420 opened 4 months ago by bobbobbio
  0

• client gets ENOSYS when running in Ubuntu 22.04 container

  #417 opened 4 months ago by bobbobbio
  1

• cargo maelstrom --stop-after=1 doesn't stop immediately while artifacts are still being built

  #414 opened 4 months ago by nfachan
  0

• The test runner viewport should grow and shrink as necessary

  #393 opened 5 months ago by nfachan
  3

• xtask distribute should be able to update binaries

  #418 opened 4 months ago by bobbobbio
  0

• Test runners should minimize the amount of movement of various widgets

  #392 opened 5 months ago by nfachan
  0

• Tests that failed the previous time they were run should be run first.

  #380 opened 4 months ago by nfachan
  0

• Use the same environment for both pytest collect/run phases

  #408 opened 5 months ago by zed
  3

• Automatically Run Automation on Pull Requests

  #413 opened 4 months ago by bobbobbio
  0

• can't update nixpkgs to the latest version

  #412 opened 4 months ago by bobbobbio
  4

• Test runners should show failed tests before summary.

  #391 opened 4 months ago by nfachan
  1

• Remote log messages get lost sometimes on shutdown

  #410 opened 4 months ago by bobbobbio
  0

• Worker starts returning errors and needs to be restarted

  #394 opened 4 months ago by nfachan
  1

• We should error when local networking is specified with a sys mount type

  #389 opened 4 months ago by nfachan
  0

• Set up Traction Data Collector

  #384 opened 5 months ago by rosok
  2

• Update documentation for `maelstrom-pytest` to clarify that it must be run in environment where `pytest` is installed

  #376 opened 5 months ago by bobbobbio
  0

• Default configuration for cargo maelstrom should forward RUST_BACKTRACE and RUST_LIB_BACKTRACE

  #386 opened 4 months ago by nfachan
  0

• cargo-maeslstrom visualizes tests not run due to not being built

  #409 opened 4 months ago by bobbobbio
  0

• Support controls to Pytest logging

  #407 opened 5 months ago by bobbobbio
  0

• Support pytest collection path filters

  #406 opened 5 months ago by bobbobbio
  0

• Support different path to pytest configuration file

  #405 opened 5 months ago by bobbobbio
  0

• Support color output from tests and test fixtures

  #404 opened 5 months ago by bobbobbio
  0

• Add support for controlling display of Python tracebacks

  #403 opened 5 months ago by bobbobbio
  0

• Add support for dealing with pytest warnings

  #402 opened 5 months ago by bobbobbio
  0

• See if we can use `--no-header` and `--no-summary` to help with pytest output scraping

  #401 opened 5 months ago by bobbobbio
  0

• Provide some way to cache test results for deterministic tests

  #400 opened 5 months ago by bobbobbio
  0

• Provide a way to run new tests (only and first)

  #399 opened 5 months ago by bobbobbio
  0

• Provide a way to select tests which failed last time

  #398 opened 5 months ago by bobbobbio
  0

• Forward `--runxfail` argument in `maelstrom-pytest`

  #397 opened 5 months ago by bobbobbio
  0

• Easy ability to run a debugger on some test

  #396 opened 5 months ago by bobbobbio
  0

• Suport listing PyTest fixtures / markers

  #395 opened 5 months ago by bobbobbio
  0

• Command Layer Placehold

  #388 opened 5 months ago by nfachan
  0

• Remove `--quiet` flag and replace functionality with new UI implementation

  #374 opened 5 months ago by bobbobbio
  0

• Show pending jobs somehow in "fancy" UI

  #387 opened 5 months ago by bobbobbio
  0

• Update `fancy` UI to only start the clock on tests when they start executing.

  #379 opened 5 months ago by nfachan
  2

• Add `--foo` CLI options as companions for any "var-args" options

  #385 opened 5 months ago by bobbobbio
  0

• Test runners provide a way to get a json file for `maelstrom-run` that runs the test exactly the same.

  #383 opened 5 months ago by nfachan
  0

• Provide a way to `maelstrom-run --tty` a shell in a container that doesn't have a shell.

  #382 opened 5 months ago by nfachan
  0

• Pytest runner doesn't work

  #375 opened 5 months ago by jscarrott
  4