Invalid binary compiled for swiftlint

[sk-]

The actions looks great, however the compiled binary for swiftlint fails with the error:

Run swiftlint --strict
  swiftlint --strict
  shell: /bin/bash -e {0}
Loading configuration from '.swiftlint.yml'
Fatal error: Loading libsourcekitdInProc.so failed: file SourceKittenFramework/library_wrapper.swift, line 39
/home/runner/work/_temp/8c14c813-f4f1-4307-b0e6-78983f636737.sh: line 1:  3112 Illegal instruction     (core dumped) swiftlint --strict
Error: Process completed with exit code 132.

Below is my configuration

  lint:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2

    - name: Install swiftlint
      uses: Cyberbeni/install-swift-tool@v2
      with:
        url: https://github.com/realm/SwiftLint
        version: "0.39.2"  # TODO: change to 0.40.3

    - name: Lint
      run: swiftlint --strict

Is there something I'm missing?

The only difference I could find with respect to the build command we have in CircleCI is that we are passing the flag --static-swift-stdlib.

Also, I noted that the tests don't execute the compiled files, they just check whether they are in the path.
ps: It'd be great if you could add https://github.com/apple/swift-format to the tests

[sk-]

I managed to make it work by running instead LINUX_SOURCEKIT_LIB_PATH=/usr/share/swift/usr/lib swiftlint --strict

[Cyberbeni]

Oh, I was not getting notifications from this repo.
Never had similar issue with SwiftFromat in my workflow, so I assumed that if it builds, it runs. I'll take a look at this issue on the weekend.

[Cyberbeni]

After a quick search it seems like this env var is the official solution for this and the we'll just have to find libsourcekitdInProc.so and export it's path on Linux.

[Cyberbeni]

Fixed in v2.1.8

[Cyberbeni]

ps: It'd be great if you could add https://github.com/apple/swift-format to the tests

That would also require some additional version matching (or specifying a fix swift version and using docker/swiftenv to download it at the start of the workflow). If you already have a working workflow for that, feel free to make a PR.

[Cyberbeni]

SInce I already knew how to do it, I added test for apple/swift-format to run after merge and on manual trigger with Swift 5.3