[Debug] Test s390x environment

[LecrisUT]

@jeertmans here is a debug workflow that would hopefully work. I'm not deeply involved into rust so I hope you can help compensate for that

[LecrisUT]

Welp it ran, but it is failing on other stuff. Locally I seem to have more luck reproducing the error:

FROM s390x/fedora:latest

RUN dnf install -y git cargo

RUN git clone https://github.com/maciejhirsz/logos /logos

WORKDIR /logos

CMD ["cargo", "test", "--workspace", "--verbose"]

You need to pass --arch/--platform flags though:

$ podman build --arch s390x -f ./Containerfile -t debug:logos-s390x
$ podman run --arch s390x debug:logos-s390x
    Finished `test` profile [unoptimized + debuginfo] target(s) in 20m 40s
     Running `/logos/target/debug/deps/logos-46a46a770371776e`

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s

     Running `/logos/target/debug/deps/logos_cli-e073d29f76d42718`

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s

     Running `/logos/target/debug/deps/tests-19e02148e7c31992`

running 5 tests
test test_codegen_fail_check ... ok
test test_codegen_check ... ok
test test_codegen_format ... FAILED
test test_codegen ... ok
test test_codegen_check_format ... FAILED

failures:

[LecrisUT]

Same issue when running docker recommendation, maybe it's a docker issue instead

[jeertmans]

There seem to be be many issues, probably unrelated to this crate, see for example:

error: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md

[LecrisUT]

Yes, I reckon it's an issue with the GH action environment. Running it locally I am able circumvent these. I couldn't find a solution to run these in a GH Actions environment. I can setup such that it runs in copr (native s390x machines) on my fork if that's an acceptable alternative

[jeertmans]

Yes, I reckon it's an issue with the GH action environment. Running it locally I am able circumvent these. I couldn't find a solution to run these in a GH Actions environment. I can setup such that it runs in copr (native s390x machines) on my fork if that's an acceptable alternative

Any alternative is fine as long as the error message / issue is the same (I mean, any bug is worth being reported), and that we can reproduce it.

[LecrisUT]

You can navigate the CI in my fork: https://github.com/LecrisUT/logos/tree/debug/s390x

Navigate to the copr build page (example) and in the log of builder-live.log search for the section Executing(%check), that is where the cargo test is being run. Feel free to make any changes in the branch it should be picked up when it build in copr

[LecrisUT]

Ok, this variant finally successfully failed: builder-live.log

[LecrisUT]

Resolved with #431