Update dependencies

[karkhaz]

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

[karkhaz]

On this run there was a 58% increase in solver runtime (59s -> 93s) for s2n-quic/quic/s2n-quic-core/slice::tests::vectored_copy_fuzz_test, will re-run just in case

[zhassan-aws]

On this run there was a 58% increase in solver runtime (59s -> 93s) for s2n-quic/quic/s2n-quic-core/slice::tests::vectored_copy_fuzz_test, will re-run just in case

This always happens mysteriously with version bumps!

[zhassan-aws]

Or rather, with many PRs. See for example this PR that adds an RFC :)

https://github.com/model-checking/kani/actions/runs/5272168064

[adpaco-aws]

Or rather, with many PRs. See for example this PR that adds an RFC :)

https://github.com/model-checking/kani/actions/runs/5272168064

Yeah, getting a couple CI failures in that PR was surprising to me. I guess the SAT procedure for benchmark is unstable? I wonder if we should start documenting the issue and keeping a list of unstable benchmarks.

[celinval]

Or rather, with many PRs. See for example this PR that adds an RFC :)
https://github.com/model-checking/kani/actions/runs/5272168064

Yeah, getting a couple CI failures in that PR was surprising to me. I guess the SAT procedure for benchmark is unstable? I wonder if we should start documenting the issue and keeping a list of unstable benchmarks.

Not surprised at all. We've been seeing this instability issue since we added this regression even for changes to the documentation.

I think adding the list of unstable tests will help, but we really need to investigate a bit more. Is Kani performance that unstable (which would be a poor experience for our users) or is this an infrastructure issue?