github-actions[bot] wrote:

<!--PREMERGE ADVISOR COMMENT: Windows-->
# :window: Windows x64 Test Results

* 51699 tests passed
* 892 tests skipped
* 1 test failed

## Failed Tests
(click on a test name to see its output)

### Clang
<details>
<summary>Clang.CodeGenObjC/expose-direct-method-opt-class-realization.m</summary>

```
Exit Code: 2

Command Output (stdout):
--
# RUN: at line 1
c:\_work\llvm-project\llvm-project\build\bin\clang.exe -cc1 -internal-isystem 
C:\_work\llvm-project\llvm-project\build\lib\clang\22\include -nostdsysteminc 
-emit-llvm -fobjc-arc -triple arm64-apple-darwin10    
-fobjc-expose-direct-methods 
C:\_work\llvm-project\llvm-project\clang\test\CodeGenObjC\expose-direct-method-opt-class-realization.m
 -o - | c:\_work\llvm-project\llvm-project\build\bin\filecheck.exe 
C:\_work\llvm-project\llvm-project\clang\test\CodeGenObjC\expose-direct-method-opt-class-realization.m
# executed command: 'c:\_work\llvm-project\llvm-project\build\bin\clang.exe' 
-cc1 -internal-isystem 
'C:\_work\llvm-project\llvm-project\build\lib\clang\22\include' -nostdsysteminc 
-emit-llvm -fobjc-arc -triple arm64-apple-darwin10 -fobjc-expose-direct-methods 
'C:\_work\llvm-project\llvm-project\clang\test\CodeGenObjC\expose-direct-method-opt-class-realization.m'
 -o -
# .---command stderr------------
# | error: unknown argument: '-fobjc-expose-direct-methods'
# `-----------------------------
# error: command failed with exit status: 1
# executed command: 
'c:\_work\llvm-project\llvm-project\build\bin\filecheck.exe' 
'C:\_work\llvm-project\llvm-project\clang\test\CodeGenObjC\expose-direct-method-opt-class-realization.m'
# .---command stderr------------
# | FileCheck error: '<stdin>' is empty.
# | FileCheck command line:  
c:\_work\llvm-project\llvm-project\build\bin\filecheck.exe 
C:\_work\llvm-project\llvm-project\clang\test\CodeGenObjC\expose-direct-method-opt-class-realization.m
# `-----------------------------
# error: command failed with exit status: 2

--

```
</details>

If these failures are unrelated to your changes (for example tests are broken 
or flaky at HEAD), please open an issue at 
https://github.com/llvm/llvm-project/issues and add the `infrastructure` label.

https://github.com/llvm/llvm-project/pull/170619
_______________________________________________
llvm-branch-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

Reply via email to