8000 Workflow runs · a16z/yices-solver · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Actions: a16z/yices-solver

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
344 workflow runs
344 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

list venv/Scripts build-windows #12: Commit 716174d pushed by 0xkarmacoma
May 17, 2025 01:34 1m 17s main
main
May 17, 2025 01:34 1m 17s
list venv/Scripts build-macos #14: Commit 716174d pushed by 0xkarmacoma
May 17, 2025 01:34 1m 12s main
main
May 17, 2025 01:34 1m 12s
list venv/Scripts build-linux #28: Commit 716174d pushed by 0xkarmacoma
May 17, 2025 01:34 3m 28s main
main
May 17, 2025 01:34 3m 28s
try running yices.exe instead of just yices build-macos #13: Commit fc1117a pushed by 0xkarmacoma
May 17, 2025 01:30 58s main
main
May 17, 2025 01:30 58s
try running yices.exe instead of just yices build-windows #11: Commit fc1117a pushed by 0xkarmacoma
May 17, 2025 01:30 1m 6s main
main
May 17, 2025 01:30 1m 6s
try running yices.exe instead of just yices build-linux #27: Commit fc1117a pushed by 0xkarmacoma
May 17, 2025 01:30 3m 25s main
main
May 17, 2025 01:30 3m 25s
fix smoke test script 10000 build-macos #12: Commit 91b6c88 pushed by 0xkarmacoma
May 17, 2025 01:27 1m 0s main
main
May 17, 2025 01:27 1m 0s
fix smoke test script build-windows #10: Commit 91b6c88 pushed by 0xkarmacoma
May 17, 2025 01:27 1m 13s main
main
May 17, 2025 01:27 1m 13s
fix smoke test script build-linux #26: Commit 91b6c88 pushed by 0xkarmacoma
May 17, 2025 01:27 3m 22s main
main
May 17, 2025 01:27 3m 22s
how does one even "activate" a "venv" on windows? build-linux #25: Commit 2abc027 pushed by 0xkarmacoma
May 17, 2025 01:25 3m 23s main
main
May 17, 2025 01:25 3m 23s
how does one even "activate" a "venv" on windows? build-macos #11: Commit 2abc027 pushed by 0xkarmacoma
May 17, 2025 01:25 1m 2s main
main
May 17, 2025 01:25 1m 2s
how does one even "activate" a "venv" on windows? build-windows #9: Commit 2abc027 pushed by 0xkarmacoma
May 17, 2025 01:25 1m 39s main
main
May 17, 2025 01:25 1m 39s
listing files explicitly in pyproject.toml doesn't work with windows … build-linux #24: Commit 2971474 pushed by 0xkarmacoma
May 17, 2025 01:21 3m 25s main
main
May 17, 2025 01:21 3m 25s
listing files explicitly in pyproject.toml doesn't work with windows … build-windows #8: Commit 2971474 pushed by 0xkarmacoma
May 17, 2025 01:21 1m 29s main
main
May 17, 2025 01:21 1m 29s
listing files explicitly in pyproject.toml doesn't work with windows … build-macos #10: Commit 2971474 pushed by 0xkarmacoma
May 17, 2025 01:21 1m 3s main
main
May 17, 2025 01:21 1m 3s
use weird 7z syntax build-linux #23: Commit 6aa47df pushed by 0xkarmacoma
May 17, 2025 01:13 3m 33s main
main
May 17, 2025 01:13 3m 33s
use weird 7z syntax build-windows #7: Commit 6aa47df pushed by 0xkarmacoma
May 17, 2025 01:13 41s main
main
May 17, 2025 01:13 41s
use weird 7z syntax build-macos #9: Commit 6aa47df pushed by 0xkarmacoma
May 17, 2025 01:13 59s main
main
May 17, 2025 01:13 59s
fix paths but for real build-windows #6: Commit d91aa2b pushed by 0xkarmacoma
May 17, 2025 01:11 33s main
main
May 17, 2025 01:11 33s
fix paths but for real build-linux #22: Commit d91aa2b pushed by 0xkarmacoma
May 17, 2025 01:11 3m 29s main
main
May 17, 2025 01:11 3m 29s
fix paths but for real build-macos #8: Commit d91aa2b pushed by 0xkarmacoma
May 17, 2025 01:11 55s main
main
May 17, 2025 01:11 55s
fix paths again build-windows #5: Commit 7ab9999 pushed by 0xkarmacoma
May 17, 2025 01:06 21s main
main
May 17, 2025 01:06 21s
fix paths again build-macos #7: Commit 7ab9999 pushed by 0xkarmacoma
May 17, 2025 01:06 1m 6s main
main
May 17, 2025 01:06 1m 6s
fix paths again build-linux #21: Commit 7ab9999 pushed by 0xkarmacoma
May 17, 2025 01:06 3m 21s main
main
May 17, 2025 01:06 3m 21s
avoid copying in /tmp on windows build-linux #20: Commit 94d8f0f pushed by 0xkarmacoma
May 17, 2025 01:04 3m 31s main
main
May 17, 2025 01:04 3m 31s
ProTip! You can narrow down the results and go further in time using created:<2025-05-17 or the other filters available.
0