@wintersteiger

Looks like the last successful windows build is from two days ago; though according to commit logs it's compiling fine on Windows.

Is there a reason the windows nightly's stopped working?

Hi,

It seems the nightly built files are all empty.
Thanks.

The releases directory hasn't been updated for over a year.

Now that Z3 4.8.5 is released here, the nightly build here is the same with the current version.
Since the bug fix of Z3Prover/z3#231 (which missed Z3 4.8.5) is crucial for me, I am looking forward to the release of the new nightly build for Z3 4.8.6 (for easier distribution of Z3).

Hi guys,

So I am curious what is your long term strategy when it comes to storing old nightly builds?

In particular, our project (SMACK) relies on the following Z3 build:
f139669240f613e86cac199e518dbc3541cf16bd

The respective binaries were moved around a couple of times, and most recently they resided here:
https://github.com/Z3Prover/bin-old/blob/f139669240f613e86cac199e518dbc3541cf16bd/z3-4.4.0.1abeb825a35a-x64-ubuntu-14.04.zip?raw=true

But now this link is broken too.

I would appreciate if you could share your long-term plans for storing Z3 nightly (Linux) builds. At this point we are thinking about hosting versions that we need on our end, but ideally we would like to avoid that.

Thanks!

The linux nightly builds are 27 days old, while the windows nightly builds are of today.

Are the linux nightly builds failing, or is something else wrong?

When using z3py with set("timeout", 600) where 600 is the ms to timeout, it is not timing out as expected.

There's no error and the process will just keep running.

Using latest release for ubuntu x64 4.5.0 release.

My environment:
Linux version 4.2.0-27-generic (buildd@lcy01-23) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #32~14.04.1-Ubuntu SMP

A bug?

This GitHub repository has been identified as a candidate for archival

This repository has had no activity in more than [x amount of time]. Long periods of inactivity present security and code hygiene risks. Archiving will not prevent users from viewing or forking the code. A banner will appear on the repository alerting users that the repository is archived.

Please see https://aka.ms/sunsetting-faq to learn more about this process.

Action

✍️

❗**If this repository is still actively maintained, please simply close this issue. Closing an issue on a repository is considered activity and the repository will not be archived.🔒

If you take no action, this repository is still inactive 30 days from today it will be automatically archived..

Need more help? 🖐️

• Email [email protected]. ✉️
• Post your questions in GitHub inside Microsoft Team in Microsoft Teams. 🗨️