| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
- run_benchmarks.py: try importing pre-built extensions before setup.py build - run_benchmarks.py: exit(1) when no backends available (was exit(0)) - run_benchmarks.py: add --require-all flag for requiring both backends - linux.yml/osx.yml: enable BUILD_NANOBIND_BENCHMARK, build benchmark targets, run from build/benchmark with --require-all Co-authored-by: peter-urban <3885740+peter-urban@users.noreply.github.com>
|
@copilot some tests are failing, please fix |
Sorry, something went wrong.
…g error - benchmark/CMakeLists.txt: always link xtensor-python for pybind11 benchmark target (was missing on APPLE, causing pybind11/pybind11.h not found) - benchmark/main_nanobind.cpp: use from_shape() instead of brace-init to fix size_t-to-double narrowing error on macOS Co-authored-by: peter-urban <3885740+peter-urban@users.noreply.github.com>
Fixed in 0fee0a7. The macOS builds were failing because:
|
Sorry, something went wrong.
|
@copilot tests are still failing, please fix |
Sorry, something went wrong.
- benchmark/CMakeLists.txt: add PRIVATE keyword to MSVC target_link_libraries to fix CMake error about mixing keyword/plain signatures - benchmark/main.cpp:429: use from_shape() instead of brace-init to fix size_t-to-double narrowing error on macOS Co-authored-by: peter-urban <3885740+peter-urban@users.noreply.github.com>
Fixed in f9bd778. Two issues:
|
Sorry, something went wrong.
|
@copilot nearly there, pybind11 is still not avaliable for windows benchmarks. |
Sorry, something went wrong.
Apply same changes as linux.yml/osx.yml: - Add -DBUILD_NANOBIND_BENCHMARK=ON to CMake configure - Build benchmark_xtensor_python and benchmark_xtensor_nanobind targets - Run benchmarks from build/benchmark with --require-all - Remove continue-on-error: true Co-authored-by: peter-urban <3885740+peter-urban@users.noreply.github.com>
Fixed in c967a1d. The Windows workflow (windows.yml) was never updated like Linux and OSX were — it was missing -DBUILD_NANOBIND_BENCHMARK=ON, the benchmark build targets, --require-all, and was still running from the source benchmark/ dir with continue-on-error: true. Now all three CI files are consistent. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
- Fix benchmark/run_benchmarks.py: try importing pre-built extensions before attempting setup.py build
- Fix benchmark/run_benchmarks.py: exit with non-zero when no backends available (sys.exit(0) → sys.exit(1))
- Fix benchmark/run_benchmarks.py: add --require-all flag to require both pybind11 and nanobind backends
- Fix .github/workflows/linux.yml: enable nanobind benchmark build, build benchmark targets, run from build dir with --require-all
- Fix .github/workflows/osx.yml: same changes as linux CI
- Fix .github/workflows/windows.yml: same changes as linux/osx CI (was missing benchmark build targets and --require-all)
- Fix macOS build: link xtensor-python on APPLE in benchmark CMakeLists.txt
- Fix macOS build: narrowing conversion error in benchmark/main_nanobind.cpp:392
- Fix Windows build: add PRIVATE keyword to MSVC target_link_libraries in benchmark CMakeLists.txt
- Fix macOS build: narrowing conversion error in benchmark/main.cpp:429
Original prompt💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.