[flang-dev] [EXTERNAL] Running the flang tests on an in-tree build

[Clement, Valentin via flang-dev]

I run only “ninja check-flang” and this run the ˜350 flang tests.

Valentin

From: flang-dev <flang-dev-bounces at lists.llvm.org> on behalf of Peter Steinfeld via flang-dev <flang-dev at lists.llvm.org>
Reply-To: Peter Steinfeld <psteinfeld at nvidia.com>
Date: Thursday, April 16, 2020 at 5:20 PM
To: "flang-dev at lists.llvm.org" <flang-dev at lists.llvm.org>
Subject: [EXTERNAL] [flang-dev] Running the flang tests on an in-tree build

I did an in-tree build of mlir and flang.  Specifically, I first created a “build” directory and then went into that directory and ran this command:

cmake -G Ninja ../llvm -DCMAKE_BUILD_TYPE=Release \
    -DLLVM_ENABLE_PROJECTS="mlir;flang" -DCMAKE_CXX_STANDARD=17 \
    -DLLVM_INSTALL_UTILS=On \
    -DCMAKE_INSTALL_PREFIX=../install

This seemed to go well.  I then ran “ninja install” which also went well.  Then I ran “ninja check-all”.  This command produced some error messages, but it seemed to run all of the flang tests and put the results in the directory “build/tools/flang/test”.  Unfortunately, though, the output did not include any summary information for the results of the flang tests.  Also unfortunately, this command said that it ran 37,839 tests, and there are only about 350 flang tests.

I have two questions –

First, what command can I execute that will only run the flang tests?

Second, how do I get a summary of which tests pass and fail?

Pete

________________________________
This email message is for the sole use of the intended recipient(s) and may contain confidential information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/flang-dev/attachments/20200417/1a854ac5/attachment-0001.html>