Skip to content

Workflows run test #228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 5 commits into from
Closed

Workflows run test #228

wants to merge 5 commits into from

Conversation

HakkyuKim
Copy link
Contributor

@HakkyuKim HakkyuKim commented Sep 24, 2021 •
edited
Loading

Test PR to verify integration tests with self-hosted runner. It will be closed after testing.

@HakkyuKim HakkyuKim mentioned this pull request Sep 24, 2021
Merged
@bwikbs
Copy link
Member

bwikbs commented Sep 26, 2021

Finally!! 😱

@HakkyuKim
Copy link
Contributor Author

@swift-kim Integration test is failing for tizen_app_control. I'm not quite familiar with ffi, do I need to set something before running? This is the partial result of the test:

(The following exception is now available via WidgetTester.takeException:)
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following _CastError was thrown running a test:
type 'Null' is not a subtype of type 'bool' in type cast

When the exception was thrown, this was the stack:
#0      new ReceivedAppControl._fromMap (package:tizen_app_control/app_control.dart:225:42)
#1      AppControl.onAppControl.<anonymous closure> (package:tizen_app_control/app_control.dart:144:50)
(elided 22 frames from dart:async and package:stack_trace)
...

The test description was:
  Can receive request from platform
════════════════════════════════════════════════════════════════════════════════════════════════════
(If WidgetTester.takeException is called, the above exception will be ignored. If it is not, then the above exception will be dumped when another exception is caught by the framework or when the test ends, whichever happens first, and then the test will fail due to having not caught or expected the exception.)
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following _CastError was thrown running a test:
type 'Null' is not a subtype of type 'bool' in type cast

When the exception was thrown, this was the stack:
#0      new ReceivedAppControl._fromMap (package:tizen_app_control/app_control.dart:225:42)
#1      AppControl.onAppControl.<anonymous closure> (package:tizen_app_control/app_control.dart:144:50)
(elided 22 frames from dart:async and package:stack_trace)
...

The test description was:
  Can receive request from platform
════════════════════════════════════════════════════════════════════════════════════════════════════
00:33 +0 -1: Can receive request from platform [E]                                                                                      
  Test failed. See exception logs above.
  The test description was: Can receive request from platform
  
00:33 +0 -1: Can send and receive request                                                                                               
(The following exception is now available via WidgetTester.takeException:)
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following ArgumentError was thrown running a test:
Invalid argument(s): Failed to lookup symbol
(/opt/usr/globalapps/org.tizen.tizen_app_control_example/bin/../lib/libflutter_tizen_wearable.so:
undefined symbol: NativeInitializeDartApi)

When the exception was thrown, this was the stack:
#0      DynamicLibrary.lookup (dart:ffi-patch/ffi_dynamic_library_patch.dart:31:29)
#1      _libEmbedder (package:tizen_app_control/src/ffi.dart)
#2      nativeCreateAppControl (package:tizen_app_control/src/ffi.dart:50:5)
#3      nativeCreateAppControl (package:tizen_app_control/src/ffi.dart)
#4      new AppControl (package:tizen_app_control/app_control.dart:73:11)
#5      main.<anonymous closure> (file:///home/hakkyu/mydir/project/flutter-project/plugins/packages/tizen_app_control/example/integration_test/tizen_app_control_test.dart:31:32)
#6      main.<anonymous closure> (file:///home/hakkyu/mydir/project/flutter-project/plugins/packages/tizen_app_control/example/integration_test/tizen_app_control_test.dart:29:47)
#7      testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:156:29)
<asynchronous suspension>
<asynchronous suspension>
(elided one frame from package:stack_trace)

The test description was:
  Can send and receive request
════════════════════════════════════════════════════════════════════════════════════════════════════
(If WidgetTester.takeException is called, the above exception will be ignored. If it is not, then the above exception will be dumped when another exception is caught by the framework or when the test ends, whichever happens first, and then the test will fail due to having not caught or expected the exception.)
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following ArgumentError was thrown running a test:
Invalid argument(s): Failed to lookup symbol
(/opt/usr/globalapps/org.tizen.tizen_app_control_example/bin/../lib/libflutter_tizen_wearable.so:
undefined symbol: NativeInitializeDartApi)

When the exception was thrown, this was the stack:
#0      DynamicLibrary.lookup (dart:ffi-patch/ffi_dynamic_library_patch.dart:31:29)
#1      _libEmbedder (package:tizen_app_control/src/ffi.dart)
#2      nativeCreateAppControl (package:tizen_app_control/src/ffi.dart:50:5)
#3      nativeCreateAppControl (package:tizen_app_control/src/ffi.dart)
#4      new AppControl (package:tizen_app_control/app_control.dart:73:11)
#5      main.<anonymous closure> (file:///home/hakkyu/mydir/project/flutter-project/plugins/packages/tizen_app_control/example/integration_test/tizen_app_control_test.dart:31:32)
#6      main.<anonymous closure> (file:///home/hakkyu/mydir/project/flutter-project/plugins/packages/tizen_app_control/example/integration_test/tizen_app_control_test.dart:29:47)
#7      testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:156:29)
<asynchronous suspension>
<asynchronous suspension>
(elided one frame from package:stack_trace)

@swift-kim
Copy link
Member

The engine containing relevant changes has not been released so the current latest version of flutter-tizen would not work.

@swift-kim
Copy link
Member

I released a new engine today. Please test again when flutter-tizen/flutter-tizen#235 lands.

@HakkyuKim
Copy link
Contributor Author

I did build the latest engine and tested this morning but forgot that I was testing on an emulator;; built an arm version. Anyways thanks for the quick update.

@HakkyuKim HakkyuKim force-pushed the workflows-run-test branch 2 times, most recently from 0a8a80b to 54226be Compare September 28, 2021 02:20
@swift-kim
Copy link
Member

The drive command works but the test command fails because the generated main generated by commands/test.dart is different from the one generated by _createEntrypoint in tizen_plugins.dart. (See flutter-tizen/flutter-tizen#228.)

The problem will be eventually fixed when #123 (comment) is applied after the Flutter 2.5 migration but you can create a PR to apply flutter-tizen/flutter-tizen#228 to commands/test.dart.

@HakkyuKim
Copy link
Contributor Author

@swift-kim
Ah, okay. Thanks for the help. I'll apply flutter-tizen/flutter-tizen#228 to commands/test.dart and try again.

@swift-kim
Copy link
Member

The migration will happen very soon so you can also just exclude tizen_app_control from testing.

@HakkyuKim
Copy link
Contributor Author

@swift-kim
Actually yes, tried applying flutter-tizen/flutter-tizen#228, but realized there are some backgrounds I'm not familiar with. The migration is ongoing so I'll exclude it and focus on running multiple self-hosted runners instead.

@HakkyuKim
Copy link
Contributor Author

Closing after test.

@HakkyuKim HakkyuKim closed this Sep 28, 2021
@HakkyuKim
Copy link
Contributor Author

Reopening to test #238.

@HakkyuKim HakkyuKim reopened this Oct 8, 2021
@github-actions github-actions bot added the tools label Oct 8, 2021
@HakkyuKim HakkyuKim force-pushed the workflows-run-test branch 2 times, most recently from 13a1b67 to 4aa077e Compare October 8, 2021 04:13
HakkyuKim and others added 3 commits October 8, 2021 13:14
@HakkyuKim
Exclude some tests
407acbe
@seungsoo47 @HakkyuKim
Update README.md (#237)
7f9740e 
* Update README.md

Add google_maps_flutter to README.md

* Update README.md

* Update README.md according to revierer's comment
@HakkyuKim
Trigger test for all packages
4aa077e
@HakkyuKim
Copy link
Contributor Author

Closing after test.

@HakkyuKim HakkyuKim closed this Oct 8, 2021
@HakkyuKim HakkyuKim deleted the workflows-run-test branch December 21, 2021 04:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
no merge This PR is not ready for merge yet p: audioplayers p: battery_plus p: camera p: connectivity_plus p: device_info_plus p: flutter_tts p: geolocator p: google_maps_flutter p: image_picker p: integration_test p: messageport p: network_info_plus p: package_info_plus p: path_provider p: permission_handler p: sensors_plus p: share_plus p: shared_preferences p: tizen_app_control p: url_launcher p: video_player p: wakelock p: wearable_rotary p: webview_flutter tools
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@HakkyuKim @bwikbs @swift-kim @seungsoo47