-
Notifications
You must be signed in to change notification settings - Fork 6k
Conversation
# Use of this source code is governed by a BSD-style license that can be | ||
# found in the LICENSE file. | ||
|
||
template("ios_app") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we add an if (is_ios)
here and assert if we're not ios and trying to use this template?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call. You can also just say assert(is_ios)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think assert(is_ios)
is fine, but we can't do what I think @gw280 is asking - we need to use this template from iOS.
<key>CFBundleName</key> | ||
<string>FlutterTests</string> | ||
<key>CFBundleVersion</key> | ||
<string>1.0</string> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to worry about the fact that these version strings are hardcoded?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the case of witing a unit testing app, no. For a real app, we'd probably want better handling of the plist in general.
testing/run_all_unittests.cc
Outdated
@@ -2,9 +2,22 @@ | |||
// Use of this source code is governed by a BSD-style license that can be | |||
// found in the LICENSE file. | |||
|
|||
#include "flutter/fml/build_config.h" | |||
#include "flutter/fml/logging.h" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Unnecessary include of logging.h
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
EXPECT_EQ(1, 1); | ||
} | ||
|
||
TEST(SmokeTest, Fail) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This requires a different harness.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now this test isn't run and nothing is tested. I wanted to see if we could somehow get the exit code from this or what log scraping might make sense for CI.
shell/platform/darwin/ios/BUILD.gn
Outdated
|
||
deps = [ | ||
":flutter_tests_fixtures", | ||
"$flutter_root/runtime:libdart", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can stop using flutter_root
now. If you still want to use it though, please use it consistently in rules (the next dep does not use the variable here).
# Use of this source code is governed by a BSD-style license that can be | ||
# found in the LICENSE file. | ||
|
||
template("ios_app") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call. You can also just say assert(is_ios)
int main(int argc, char** argv) { | ||
#ifdef OS_IOS | ||
asl_log_descriptor(NULL, NULL, ASL_LEVEL_NOTICE, STDOUT_FILENO, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this harness, both can be ASL_LEVEL_ERR. I don't think notices are shown by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In a local test they were, but I'll just make them both err.
[email protected]:flutter/engine.git/compare/ed1557f82dd4...f237896 git log ed1557f..f237896 --no-merges --oneline 2019-10-10 [email protected] Roll src/third_party/dart cc3e22f724..48e93d3d3b (8 commits) 2019-10-10 [email protected] Roll fuchsia/sdk/core/mac-amd64 from pczjK... to xd5Jj... (flutter/engine#13055) 2019-10-10 [email protected] Minimal test harness for iOS (flutter/engine#13029) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll Please CC [email protected] on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
[email protected]:flutter/engine.git/compare/ed1557f82dd4...f237896 git log ed1557f..f237896 --no-merges --oneline 2019-10-10 [email protected] Roll src/third_party/dart cc3e22f724..48e93d3d3b (8 commits) 2019-10-10 [email protected] Roll fuchsia/sdk/core/mac-amd64 from pczjK... to xd5Jj... (flutter/engine#13055) 2019-10-10 [email protected] Minimal test harness for iOS (flutter/engine#13029) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll Please CC [email protected] on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
This reverts commit 0622b05.
This reverts commit 0622b05.
This reverts commit 0622b05.
To run:
Then use either Console.app or
xcrun simctl spawn booted log stream
, launch the app, and look at the log output.It would probably be nicer to bootstrap this from XCTest instead.
Known issues: