Disable buggy LTO

[Veetaha]

Fixes marker_rustc_driver crashing on windows with exit code: 0xc0000005, STATUS_ACCESS_VIOLATION. Reported in #318 (comment).

I disabled LTO, in release build and it fixes the problem.

I extended the CI to perform a really simple release smoke test both for the current release and for the previous release (in github action test CI job).

Here, for example, you may see that the bug reproduces in master on the changed CI

• CI job for the current version of marker
• CI job for the released version of marker

With the disabled LTO release-smoke-test passes

Btw. @xFrednet could you add the release-smoke-test jobs to required ones please?

[xFrednet]

Thank you for finding the issue so quickly and the new CI test ❤️

Do we want to release v0.4.2 with this patch? In that case, could you update the changelog entry?

could you add the release-smoke-test jobs to required ones please?

Yes of course! I'll add it, once this PR is done with the merge queue.

[Veetaha]

Yes, let's do a 0.4.2. Btw. each patch release breaks our CI workflow, which is pinned to a specific cargo-marker version in a docker image, and it complains that marker_api 0.4.1 isn't compatible with 0.4.0 (which it should be, that problem is tracked in #225). Though, it's not a big deal for me to update the version and make a new image, still a good reminder for me that #307 needs to be implemented 😅

---

I think you'll need to merge this one bypassing the CI status checks because github actions test on windows is going to be red until 0.4.2 is released

[Veetaha]

I have no idea what happened there, so I just squashed cargo release into a single command, since single invocation works.

[Veetaha]

There was also this hang on driver ARM build. I also have no idea what happened there. It could be a bug in rustc or qemu. I just reduced the timeout to 60 minutes. For me the build works fine and finishes within ~11 minutes.

[xFrednet]

LGTM, that's another bug down!

Let's get the v0.4.2 party started :D

[xFrednet]

And the smoke tests have been added to the CI requirements :D