This is an archive of the discontinued LLVM Phabricator instance.

[libunwind] Update the test configuration files to support the remote execution.
ClosedPublic

Authored by vvereschaka on Apr 15 2022, 7:50 PM.

Details

Summary

These changes allow remote execution for the libunwind library tests.

Diff Detail

Event Timeline

vvereschaka created this revision.Apr 15 2022, 7:50 PM
Herald added a reviewer: Restricted Project. · View Herald TranscriptApr 15 2022, 7:50 PM
Herald added a project: Restricted Project. · View Herald Transcript
vvereschaka requested review of this revision.Apr 15 2022, 7:50 PM
Herald added a project: Restricted Project. · View Herald TranscriptApr 15 2022, 7:50 PM

@ldionne, would you take a look? I would like to restart our ARMv7 win-to-linux cross builder with these new configuration files, but they don't work with the remote test execution properly.

https://lab.llvm.org/buildbot/#/builders/60

ldionne accepted this revision.Apr 25 2022, 2:01 PM

This looks reasonable to me, but I have a question.

libunwind/test/configs/llvm-libunwind-shared.cfg.in
23

Why do you need this bit? Same for the static configuration.

This revision is now accepted and ready to land.Apr 25 2022, 2:01 PM
vvereschaka added inline comments.Apr 25 2022, 3:48 PM
libunwind/test/configs/llvm-libunwind-shared.cfg.in
23

I just did it in the same way as it done for libcxx tests. The target_info property is still used within the libcxx test framework files, such as libcxx/utils/libcxx/test/config.py and libcxx/utils/libcxx/test/target_info.py.