[libcxx-commits] [PATCH] D90068: [libc++] Perform libc++ CI directly in the pipeline instead of triggering our own pipeline
Louis Dionne via Phabricator via libcxx-commits
libcxx-commits at lists.llvm.org
Mon Nov 2 06:12:20 PST 2020
ldionne added a comment.
In D90068#2361518 <https://reviews.llvm.org/D90068#2361518>, @goncharov wrote:
> In D90068#2351068 <https://reviews.llvm.org/D90068#2351068>, @ldionne wrote:
>
>> However, another way we could perhaps achieve proper reporting is if we moved the reporting step that's currently run in the `premerge-checks` pipeline into the `libcxx-ci` pipeline. Would that work? I assume the reporting step isn't strongly tied to the `premerge-checks` pipeline?
>
> I think that it should be possible to modify reporting so it will look closer on the result of libcxx pipeline and keep it separate.
> How do you image proper reporting should look like? Would you like to see links to the failed configurations (like we have for windows / linux), e.g. by adding "libcxx C++03" next to the build or something else?
I haven't really thought about how that should work, however I think it would make sense to give it exactly the same handling as the normal jobs on the `premerge-checks` pipeline (i.e. Linux and Windows currently).
If you think it's possible to keep the libcxx-ci in a separate pipeline, do you think it would be possible to have the link here point to the libcxx-ci pipeline directly? F13645972: Screen Shot 2020-11-02 at 09.11.44.png <https://reviews.llvm.org/F13645972>
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D90068/new/
https://reviews.llvm.org/D90068
More information about the libcxx-commits
mailing list