Closed lacasseio closed 5 years ago
@lacasseio does this only happen sometimes or fail in multiple ways? When I run just XcodeErrorIntegrationTest
locally, I don't see a failure from the IDE or on the command-line.
I'm on macOS 10.14.1 and I have:
$ xcodebuild -version
Xcode 10.1
Build version 10B61
However, I do see failures with XcodeMultipleSwiftProjectIntegrationTest
and XcodeSingleSwiftProjectIntegrationTest
, but they don't look like problems with the console output. produces reasonable message when xcode uses outdated xcode configuration
does look console output related.
There’s another error that seems to be happening with some Swift tests related to asserting what intermediate files are being generated. It fails on a .swiftdeps~moduleonly
file and could figure out. I was going to look a bit more into it today. The scrambled output seems to be repeatable, but I didn't try to see if it was flaky in any way.
I'm on macOS 10.13.6 and I have:
xcodebuild -version
Xcode 10.1
Build version 10B61
Now this seems to be flaky on my machine...
Since I'm still getting the error despite the change, I did another research and found this: https://gitlab.kitware.com/cmake/cmake/issues/18088 and the fix seems to be https://gitlab.kitware.com/cmake/cmake/merge_requests/2151/diffs at the moment. If we confirm this fix, we will need to split out an issue to support the new Xcode build system.
I can confirm it works. I will roll the previous change in favor of this new one instead and open another issue to priotize a better Xcode 10 support. At the same time, we may loose support for previous IDE version support but given everything is delegated to Gradle, I would say it's alright. //cc @big-guy What do you think?
Issue https://github.com/gradle/gradle-native/issues/956 was opened to properly move away from the legacy build system.
It could also be an issue arising from how we detect rich vs plain console.
Expected Behavior
The new behavior breaks the output scraping used during the tests.
Current Behavior
The Gradle output when using Xcode 10 looks like the following. Notice how some lines are split in half compared to a normal output.
The following tests are affected by this new behavior:![Screen Shot 2018-11-28 at 10.02.32 AM.png](https://images.zenhubusercontent.com/57f3842a95e42b6c5ba9dabb/0e0ec3db-bd01-4eaf-b300-be4e12e038aa)
Context
Steps to Reproduce (for bugs)
Your Environment