-
Notifications
You must be signed in to change notification settings - Fork 52
Add integration test workflow #169
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.
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
Add integration test workflow #169
Conversation
|
please, rebase first |
|
We can now merge this after adding a self-hosted runner for this repository. |
bwikbs
left a comment
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.
Oh! This is what I'm looking forward to personally! 🔥
@HakkyuKim Is our self-hosted runner ready? |
|
@bbrto21 I'm working on something else in our internal git at the moment, I'll bring it up next Monday! |
|
I'm really sorry about the delay, setting up a server inside the company is a slow process... |
|
To share the process so far...I'm requesting one security approval after another. Apparently some urls are blocked by firewalls even with extern network, unfortunately GitHub is one of them. |
|
The test server can now listen to Github workflows from an external network, https://github.com/HakkyuKim/plugins/pull/14/checks?check_run_id=3585756046. However, wearable emulators just randomly crash even when no app is running. Mobile and TV emulators can't even get booted. I'm planning to reinstall the host OS, file an issue to Tizen SDK team, or use another server machine. |
|
Reinstalling the OS did not work, I've filed an issue to Tizen SDK team. |
|
The test server finally works, @swift-kim could you grant me the permission to add self-hosted runner for this repo so I can test this out? |
|
Should workflow be merged after setting multiple self-hosted runners with different device profiles? If this PR is merged, only a single self-hosted runner will be used for CI, testing plugin integration test on wearable-5.5 emulator. #229 and #232 are required to run multiple self-hosted runners with different device profiles. |
bbrto21
left a comment
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.
LGTM
I think it's meaningful even if it test plugins only on wearable emulator.
and if we use this, we may find new issues that we didn't expect.
|
Let's merge #229 first so we can add the |
- Split long command to multiple lines. - Remove commented code.
- Remove setting legacy variable. - Remove `pwd` and use dot syntax when referencing from repo root. - export path variable with custom path first.
wifi_info -> wifi_info_flutter
* Update workflow script * Use latest flutter-tizen - Split long command to multiple lines. - Remove commented code. * Exclude tizen_app_control from test * Clarify a name in workflow step * Remove unnessary condition check * Use checkout actions for flutter-tizen install - Remove setting legacy variable. - Remove `pwd` and use dot syntax when referencing from repo root. - export path variable with custom path first. * Fix incorrect package name wifi_info -> wifi_info_flutter * Use --platforms option
Github workflows script that runs integration test on pull requests. This PR should be merged after setting up self-hosted runner.
Notes:
Testing done on #228.