Mizux Seiha
Mizux Seiha
could be linked to https://github.com/bazelbuild/rules_jvm_external/commit/8391c5bcde3133a270837c1287b94240a5c71b34 ?
FYI, I'm currently rebasing this branch on main since the merge of the PR for aarch64 Windows conflict... EDIT: my bad rebase on main is borken but merging was ok...
```sh [^v^]─corentinl@corentinl-macbookpro2 %CTEST_OUTPUT_ON_FAILURE=1 cmake --build build --target test -v Running tests... /opt/homebrew/Cellar/cmake/3.26.4/bin/ctest --force-new-ctest-process Test project /Users/corentinl/work/cpu_features/build Start 1: bit_utils_test 1/4 Test #1: bit_utils_test ................... Passed 0.00 sec Start 2: string_view_test...
sysctl on M1: https://gist.github.com/Mizux/fc3309b1efeb1454cc7b093c5f23992e (ed `system_profiler SPHardwareDataType` seems cool to identify device model)
Just for the record is it this commit ? https://github.com/dgud/wings/commit/cacf19d40256e44a56b6432144802e5091f2a280
looking at https://github.com/protocolbuffers/protobuf/blob/master/.github/mergeable.yml I would try to add "release notes: yes" in the body of the commit message, my guess the `CHANGE.txt` is autogenerated using commit message "tags" etc...
see #337 ....
@johnb003 I would say the problem is madler who lets zlib not maintained and don't let us (the OSS community) having an OSS Community Modern CMake based build... > 5....
hi sorry for the delay, never saw it before.... Is is constantly failing or just flaky ? Le mer. 3 janv. 2024 à 01:09, Miles Lubin ***@***.***> a écrit :...
the MacBookPro I've used to build the python 3.11 wheel is using python 3.11.0 from python.org your CI seems to use python 3.11.7 (https://github.com/cvxpy/cvxpy/actions/runs/7381279576/job/20296022928?pr=2316#step:6:15) and from condaforge install `python_abi-3.11` (https://github.com/cvxpy/cvxpy/actions/runs/7381279576/job/20296022928?pr=2316#step:5:77)...