Skip to content
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

wasmtime: 0.36.0 -> 0.37.0 #173870

Merged
merged 1 commit into from
May 22, 2022
Merged

Conversation

ereslibre
Copy link
Member

Description of changes
Things done
  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 22.05 Release Notes (or backporting 21.11 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
    • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
  • Fits CONTRIBUTING.md.

@Mic92
Copy link
Member

Mic92 commented May 21, 2022

@GrahamcOfBorg build wasmtime

@Artturin Artturin added the 12.approvals: 1 This PR was reviewed and approved by one reputable person label May 22, 2022
@ereslibre ereslibre force-pushed the bump-wasmtime-0-37 branch 2 times, most recently from 6105156 to 4fd3b59 Compare May 22, 2022 07:24
Re-enable darwin platform.
@ereslibre ereslibre force-pushed the bump-wasmtime-0-37 branch from 4fd3b59 to dc34b6e Compare May 22, 2022 07:26

# This environment variable is required so that when wasmtime tries
# to run tests by using the rusty_v8 crate, it does not try to
# download a static v8 build from the Internet, what would break
# build hermetism.
RUSTY_V8_ARCHIVE = "${v8}/lib/libv8.a";
RUSTY_V8_ARCHIVE = lib.optionalString stdenv.isLinux "${v8}/lib/libv8.a";
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Force pushed to replace lib.optionals with lib.optionalString.

@happysalada
Copy link
Contributor

The ci is happy, and I can't see anything to change.
Thank you for this!

@happysalada happysalada merged commit 593dfc4 into NixOS:master May 22, 2022
@ereslibre ereslibre deleted the bump-wasmtime-0-37 branch May 22, 2022 11:56
@nomeata
Copy link
Contributor

nomeata commented Aug 19, 2022

@ereslibre ,looks like wasmtime was removed on Darwin again, in: #173671. I wonder why…

@ereslibre
Copy link
Member Author

@nomeata I will have a look at it; can see that hydra reports a failure on x86_64-darwin at https://hydra.nixos.org/build/187449906; apparently since wasmtime 0.37 back in May 22nd (https://hydra.nixos.org/build/177848118). I didn't realize this one and I actually removed the broken attribute in #178457 because I could not see any issue at all 🤦

I will try to reproduce what hydra is reporting and mark the package as broken or try to fix the build...

@ereslibre
Copy link
Member Author

ereslibre commented Aug 19, 2022

This is probably an issue with the runtime trying to use certain CPU capabilities, errors in the log https://hydra.nixos.org/build/186536905/nixlog/1: Unsupported feature: SIMD support requires SSE3, SSSE3, SSE4.1, and SSE4.2 on x86_64.' in several places.

I will check later today and disable tests for x86_64-darwin with a comment on why tests are disabled. It's not an optimal solution because we lose that feedback on that platform, but the failure is very tied to the execution environment on x86_64-darwin on the hydra infrastructure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants