-
Notifications
You must be signed in to change notification settings - Fork 811
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate the create-exe functionality outside of wasmer #4285
Comments
Here are some notes for whoever picks this one up. This isn't the first time we've disabled create-exe tests (see #3615). Probably the most common error we see is around linking and undefined symbols. See this build from #4229 (ironically, this PR was created to automatically retry these flaky tests).
We've also seen errors where the runner runs out of disk space. This might be because caching exhibits unbounded growth or our custom caching mechanism is downloading half the internet. Maybe the periodic job to clean up cache buckets every day needs to run more often or we need to be more selective in what we cache/reuse. |
Ignore all create_exe tests as part of #4285
create-exe
spuriously fail, usually because of linking errors.Ideally, we should move
create-exe
to outside the wasmer crate, so we can test and build this functionality separately of the main CI (to both speed up the builds, and avoid errors in CI).Meanwhile, we will
#[ignore]
the tests to avoid errorsThe text was updated successfully, but these errors were encountered: