summaryrefslogtreecommitdiff
path: root/.github
Commit message (Collapse)AuthorAgeFilesLines
* Update flake8 and fix errors (#7172)Thomas Lively2024-12-201-1/+1
| | | | | | | | | The flake8 we were running on CI was too old and began giving spurious errors about the uninterpreted contents of f-strings. Update to the latest flake8 and fix all the new errors, including the previously incorrect comment syntax in the .flake8 file. Also remove scripts/storage.py, since it didn't seem to be used for anything we currently need.
* [CI] Fix GitHub error due to deprecated artifact uploading v1 (#6900)Alon Zakai2024-09-041-1/+1
|
* Upgrade setup-python and checkout actions in CI (#6533)Thomas Lively2024-04-241-23/+24
| | | | This will hopefully get setup-python to install Python for the correct architecture now that the macos runners have switched to ARM.
* Fix ASan/TSan errors by using LLVM 18 (#6396)Alon Zakai2024-03-141-8/+16
| | | | | Github actions CI started to fail for no obvious reason. It seems some VM change happened, and very recent LLVM/clang is needed to keep running sanitizers. LLVM 18 is the first version that works.
* Add a WebAssembly build to release (#6351)Alon Zakai2024-02-271-0/+66
| | | | | | | | | | | | | | | | | | | Simply build wasm-opt with Emscripten and bundle that up. Example build: https://github.com/kripken/binaryen/releases/tag/wasm-build-1 Specifically binaryen-wasm-build-1-wasm.tar.gz Only 1.72 MB, as it's just wasm-opt and not any other tool, so it is much smaller than our other targets. Perhaps we will add more of the tools later as needed (wasm-metadce, wasm-split, etc.). Also update the readme regarding which toolchains use us as a library, that I noticed while editing it to add the release platforms.
* Build and release on aarch64 (#6334)Darren Worrall2024-02-231-3/+12
| | | Fixes #6311
* [CI] Use --break-system-packages on Alpine (#6167)Alon Zakai2023-12-111-1/+1
| | | Something changed in how CI sets up Python and now this is needed to avoid an error.
* Use clang 15 to avoid ASan test flakes that 14 has (#6125)Alon Zakai2023-11-161-1/+7
| | | Seems to fix #6116
* Fix build failure on older Ubuntu (#6085)Thomas Lively2023-11-071-1/+2
| | | | Update the C++20 builder to use Ubuntu 20.04 to catch problems building with its system compiler. Also fix such a problem in wasm-fuzz-lattices.cpp.
* [analysis][NFC] Use C++20 concepts for Lattice (#6027)Thomas Lively2023-10-181-1/+37
| | | | | | | | | | | | | Replace the static assertions ensuring that Lattice types have the necessary operations with a C++20 concept called `Lattice`. To avoid name conflicts with the new concept, rename existing type parameters named `Lattice` to `L`. When not building with C++20, `Lattice` is a macro that resolves to `typename` so the code continues compiling and has the same behavior, but without any eager checks of the requirements on lattices. Add a new C++20 builder to CI to ensure that future changes compile with both C++17 and C++20. Once we switch to C++20 by default, the new builder can be removed. Update the lint builder to use a recent clang-format that understands concepts.
* Configure codecov to be less intrusive (#6000)Thomas Lively2023-10-061-0/+3
| | | Disable codecov GitHub comments and PR-specific coverage checks.
* Disable inline CodeCov annotations (#5872)Thomas Lively2023-08-101-0/+3
| | | | While useful these annotations in the GitHub code review UI, are also extremely intrusive and make reading code under review harder.
* Configure CodeCov to be informational only (#5863)Thomas Lively2023-08-081-0/+5
| | | | Add a codecov.yml file configuring CodeCov to be in informational mode, meaning that it will never report a failure.
* Add CodeCov to CI (#5856)Thomas Lively2023-08-031-0/+34
| | | | | | Add a CI step to build with gcov instrumentation and run the lit test suite to gather profiles, then upload those profiles to codecov.io to generate a code coverage report for each PR. The goal is not necessarily to achieve 100% code coverage, but rather to help find important missing test cases and dead code.
* Remove unnecessary LLVM path addition in CI (#5520)Changqing Jing2023-02-241-2/+0
|
* Remove `-sEXPORT_ES6` + Node.js workaround for binaryen.js (#5235)Kleis Auke Wolthuizen2022-11-211-4/+12
| | | This workaround is no longer needed after commit emscripten-core/emscripten@ce4c405.
* Pin Emscripten (#5100)Thomas Lively2022-09-301-2/+4
| | | | | The current CI breakage is due to https://github.com/emscripten-core/emscripten/pull/17948. Pin the Emscripten version used in CI until that can be investigated and resolved.
* Revert "Pin the emsdk for now (#5077)" (#5078)Alon Zakai2022-09-221-4/+2
| | | | | This reverts commit 6cc44fd11ba550ea7149fbc868a9b70aa58822a6. #5075 fixes the require() issue, so we don't need the pin.
* Pin the emsdk for now (#5077)Alon Zakai2022-09-221-2/+4
| | | See emscripten-core/emscripten#17851
* Setup git submodules so googletest is fetched, unbreaking alpine in releases ↵Alon Zakai2022-05-041-0/+2
| | | | | | | | | (#4640) Without this the CMake step fails on not finding googletest/googletest/src/gtest_main.cc Fixes #4639
* Fix CMake builds on CI (#4578)Alon Zakai2022-04-041-5/+5
| | | | | | | | | | Add -DCMAKE_INSTALL_PREFIX=out/install to all builds. This is now needed on CI for some reason that I cannot figure out. Fixes #4576 Fixes #4575
* Add '-vv' verbosity to binaryen-lit tests (#4577)Thomas Lively2022-04-041-2/+2
| | | To help debug them when they go wrong, as seems to be happening on #4574.
* Introduce gtest (#4466)Thomas Lively2022-01-201-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | Add gtest as a git submodule in third_party and integrate it into the build the same way WABT does. Adds a new executable, `binaryen-unittests`, to execute `gtest_main`. As a nontrivial example test, port one of the `TypeBuilder` tests from example/ to gtest/. Using gtest has a number of advantages over the current example tests: - Tests are compiled and linked at build time rather than runtime, surfacing errors earlier and speeding up test execution. - Tests are all built into a single binary, reducing overall link time and further reducing test overhead. - Tests are built from the same CMake project as the rest of Binaryen, so compiler settings (e.g. sanitizers) are applied uniformly rather than having to be separately set via the COMPILER_FLAGS environment variable. - Using the industry-standard gtest rather than our own script reduces our maintenance burden. Using gtest will lower the barrier to writing C++ tests and will hopefully lead to us having more proper unit tests.
* Build ARM64 MacOS releases (#4397)Derek Schuff2022-01-052-5/+31
| | | There is now a new zip file in each release with 'arm64' in its name, to go along with the x86_64 package.
* Remove python from CMake build (#4324)Blaine Bublitz2022-01-041-3/+0
| | | Use CMake's configure_file() instead.
* Fix filenames in create_release CI workflow (#4366)Sam Clegg2021-12-091-2/+2
|
* Switch to new github actions (`softprops/action-gh-release`) for building ↵Sam Clegg2021-12-011-40/+20
| | | | | releases. NFC (#4362) Fixes: #4148
* [CI] Fix alpine builds (#4284)Max Graey2021-10-281-1/+1
| | | It seems that now alpine requires pip3.
* Revert accidental debugging changes from #3935 (#3950)Thomas Lively2021-06-221-3/+3
|
* Preserve function heap types during text parsing (#3935)Thomas Lively2021-06-221-3/+3
| | | | | | | | | | | | | | Previously, ref.func instructions would be assigned the canonical (i.e. first parsed) heap type for the referenced function signature rather than the HeapType actually specified in the type definition. In nominal mode, this could cause validation failures because the types assigned to ref.func instructions would not be correct. Fix the problem by tracking function HeapTypes rather than function Signatures when parsing the text format. There can still be validation failures when round-tripping modules because function HeapTypes are not properly preserved after parsing, but that will be addressed in a follow-up PR.
* Create a shasum file for the Windows tarball (#3832)Роман Донченко2021-04-221-9/+3
| | | | | | CMake has a `sha256sum` subcommand that can be used to calculate checksums portably. Use it in the release workflow to create checksums on Windows. For consistency, use it on macOS and Linux too.
* Perform clang-tidy/clang-format linting only on PRs (#3708)Sam Clegg2021-03-181-2/+5
| | | | These steps diff between a PR and upstream which doesn't really make sense for normal CI runs.
* ci: build alpine linux to match what the release builder does (#3642)Sam Clegg2021-03-022-0/+39
| | | | | | Also fix the underlying issue which was that `lit` was not being correctly installed via pip3. See #3459
* Replace "master" with "main" in scripts and docs (#3502)Thomas Lively2021-01-191-1/+1
| | | | We have updated the default branch name from "master" to "main." This PR updates scripts, configurations, and docs to reflect this change.
* Enable LTO on the Linux Clang build on CI (#3491)Derek Schuff2021-01-141-3/+3
| | | Also adjust the check for Clang to also match AppleClang
* Improve lit support (#3426)Sam Clegg2020-12-091-0/+5
| | | | | | | | This uses the same technique used in llvm-lit to enable running on in-tree tests with out-of-tree builds. So you can run something like this: ../binaryen-out/bin/binaryen-lit test/lit/
* Introduce lit/FileCheck tests (#3367)Thomas Lively2020-11-181-1/+12
| | | | | | | | | | | | | | | lit and FileCheck are the tools used to run the majority of tests in LLVM. Each lit test file contains the commands to be run for that test, so lit tests are much more flexible and can be more precise than our current ad hoc testing system. FileCheck reads expected test output from comments, so it allows test output to be written alongside and interspersed with test input, making tests more readable and precise than in our current system. This PR adds a new suite to check.py that runs lit tests in the test/lit directory. A few tests have been ported to demonstrate the features of the new test runner. This change is motivated by a need for greater flexibility in testing wasm-split. See #3359.
* Add requirements-dev.txt (#3377)Thomas Lively2020-11-161-1/+1
| | | | | This file makes it simple for users and CI bots to install all the Python dev dependencies necessary to run the test suite. Right now it only contains flake8, but soon it will contain lit and filecheck as well (see #3367).
* Remove deprecated ::add-path:: command from actions (#3374)Thomas Lively2020-11-161-2/+4
|
* Fix MinGW build & add to GitHub Actions (#3287)Blaine Bublitz2020-10-261-0/+16
| | | | - Add a MinGW CI build - Add compiler flag to successfully build on MinGW
* Enable LeakSanitizer on CI again (#3106)Daniel Wirtz2020-09-081-2/+1
| | | LSan had to be disabled a while ago due to issues with CI runners, but these problems have been resolved indirectly meanwhile by switching to GitHub Actions. Turned out that a few new problems slipped through since then due to not checking anymore, but these are fixed now, so LSan can be enabled again.
* Fix installation phase in build_release.yml (#3054)Sam Clegg2020-08-171-2/+2
| | | Followup on #3052
* Include full `install` in releases (#3052)Sam Clegg2020-08-172-12/+12
| | | | | | This means we will also include any headers or libraries that are part of the `install` step. Fixes: #3048
* Skip tests that fail on windows and enable all the rest (#3035)Alon Zakai2020-08-111-3/+0
| | | | | | | | | | | | | | This lets us run most tests at least on that platform. Add a new function for skipping those tests, skip_if_on_windows, so that it's easy to find which tests are disabled on windows for later fixing efforts. This fixes a few minor issues for windows, like comparisons should ignore \r in some cases. Rename all passes tests that use --dwarfdump to contain "dwarf" in their name, which makes it easy to skip those (and is clearer anyhow).
* Fix github actions for releases (#2965)Sam Clegg2020-07-192-14/+17
| | | | | | | Also, perform cmake --install before archive assets during normal CI builds. This means we include the binaryen shared library on platforms that use it. Fixes: #2946 #2962
* Mimic MODULARIZE_INSTANCE (#2838)Daniel Wirtz2020-05-071-2/+2
| | | | | | | Turned out that the behavior of MODULARIZE_INSTANCE, which has been removed from Emscripten lately, cannot be easily reproduced using MODULARIZE. So, instead of modularizing and attempting to undo it, this just uses some good old wrapper code to achieve the same.
* Fix emscripten CI tests to 1.39.14, until we fix the lack of ↵Alon Zakai2020-05-061-2/+2
| | | | MODULARIZE_INSTANCE (#2834)
* Use emscripten latest, as tot has removed MODULARIZE_INSTANCE which we use ↵Alon Zakai2020-05-051-2/+2
| | | | | | (#2830) We need to find another approach than MODULARIZE_INSTANCE, which is not trivial. This unbreaks CI for now.
* CI: Use stripped release builds for distribution (#2826)Sam Clegg2020-05-042-10/+30
| | | | | | | | | | | Even though `Release` is the default configuration for make better to be explicit. Also, for windows build we need to make sure we pass `--config Release` when actually building since the projects files will build Debug by default regardless of CMAKE_BUILD_TYPE. Fixes: #2825
* CI: Trigger on pull_request (#2801)Sam Clegg2020-04-241-1/+6
|
generated by cgit v1.2.3 (git 2.39.1) at 2025-04-04 11:03:05 +0000