OpenBLAS

78 MB

Branch: develop

Author	SHA1	Message	Date
guoyuanplct	7732a55200	Add retry mechanism after deadlock timeout for c910v.	8 months ago
Han Gao	1f687b2f60	Bump xuantie qemu for c910v Signed-off-by: Han Gao <rabenda.cn@gmail.com>	9 months ago
Martin Kroeker	7c3a920a81	CI: Update ubuntu-latest runners to fix side effects of switch to 24.04 (#5079 )	1 year ago
gxw	d9e2db3735	CI: add openblas_utest_ext for c910v, mips64 and loongarch64	1 year ago
Han Gao/Revy/Rabenda	304a9b60af	Update T-Head toolchains v2.8.0 Signed-off-by: Han Gao/Revy/Rabenda <rabenda.cn@gmail.com>	2 years ago
Ralf Gommers	2418a20f1f	Cancel running CI jobs when new changes are pushed to a PR The `group` expression ensures that the cancel-in-progress behavior is to only cancel if a new commit is pushed to the PR for which the job is running, not other PRs. This is a fairly standard snippet, used also in CI jobs for NumPy and other projects.	2 years ago
Ralf Gommers	1d4ed20c2f	Add conditions to all CI jobs to only run on main repo by default This is a follow-up to gh-4271. At the moment, when a contributor pushes the latest `develop` to their own branch to bring their own fork in sync with `main`, or if they push another branch, this triggers 30 CI jobs to run. Most will complete silently and only burn CPU time unnecessarily. If there's a failure, this may result in unexpected failure notifications. And the AWS Graviton3 run won't complete at all and time out, since the Cirun hook will only work when triggered from the main repo.	2 years ago
Han Gao	7b16c4c051	CI (C910V): add test Signed-off-by: Han Gao <gaohan@iscas.ac.cn>	2 years ago

8 Commits (develop)