Skip to content

CI: benchmark job failing #24482

@ngoldbaum

Description

@ngoldbaum

The benchmark job started failing because asv had its first release in more than a year yesterday:

+ python /home/runner/work/numpy/numpy/builds/venv/bin/asv dev -q
Couldn't load asv.plugins.mamba because
No module named 'mamba'
Traceback (most recent call last):
  File "/home/runner/work/numpy/numpy/builds/venv/bin/asv", line 8, in <module>
    sys.exit(main())
  File "/home/runner/work/numpy/numpy/builds/venv/lib/python3.9/site-packages/asv/main.py", line 29, in main
    result = args.func(args)
  File "/home/runner/work/numpy/numpy/builds/venv/lib/python3.9/site-packages/asv/commands/__init__.py", line 49, in run_from_args
    return cls.run_from_conf_args(conf, args)
  File "/home/runner/work/numpy/numpy/builds/venv/lib/python3.9/site-packages/asv/commands/run.py", line 166, in run_from_conf_args
    return cls.run(
  File "/home/runner/work/numpy/numpy/builds/venv/lib/python3.9/site-packages/asv/commands/dev.py", line 24, in run
    raise RuntimeError(
RuntimeError: `asv dev` has been removed. It was a shortcut of `asv run`, which you can use instead. It was removed because it caused confusion, in particular after changing what it was running in asv 0.5.x

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions