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
Kotlin workflow-ui-* re-org. #915
Conversation
I wasn’t quite able to stick the landing. The bulk of the re-org is done, everything compiles, almost everything runs. But. A few samples (Dungeon, Tic Tac Toe, ToDo) crash at launch with a horrible stack trace that starts I assume this is something messed up in my environment, but I can't figure out what and I'm out of time. Also, the loss of the default bindings (totally the right call!) really brings home how unpleasant the runtime nature of |
Sample stack trace:
|
8b038ce
to
c05e0a1
Compare
The weird compilation error was due to the overly-general This seems to work, but a bunch of UI tests are flaking extremely hard, so even if this PR goes green it might not be great to merge it yet. However the tests don't flake when run in isolation, so I'm wondering if this is the same flakiness Ray noticed last week. |
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.
Thank you! This is going to help us a lot!
...n/samples/todo-android/common/src/main/java/com/squareup/sample/todo/TodoListsAppWorkflow.kt
Show resolved
Hide resolved
c05e0a1
to
1ce53c1
Compare
Addressed comments, will merge on green. |
I should say, flake locally when run en masse. That's what I tried to fix
with orchestrator, but it's flaky in its own right.
…On Sat, Feb 1, 2020, 6:43 AM Ray Ryan ***@***.***> wrote:
Having them flake locally is not surprising. It's mostly, but not
completely fixed by disabling animation :/ How do they do on ci?
On Fri, Jan 31, 2020, 7:22 AM Zach Klippenstein ***@***.***>
wrote:
> The weird compilation error was due to the overly-general
> packagingOptions exclusion. I reverted that, added only the ones it
> complained about, and moved it into the single root build.gradle file so
> it's not duplicated everywhere.
>
> This seems to work, but a bunch of UI tests are flaking *extremely*
> hard, so even if this PR goes green it might not be great to merge it yet.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#915?email_source=notifications&email_token=AAOMCHMUBPXAMD47MZ4VGKDRANVMXA5CNFSM4KLOQVT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKNBSLA#issuecomment-580524332>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAOMCHKOHFSEBXM7P47EJ33RANVMXANCNFSM4KLOQVTQ>
> .
>
|
Having them flake locally is not surprising. It's mostly, but not
completely fixed by disabling animation :/ How do they do on ci?
…On Fri, Jan 31, 2020, 7:22 AM Zach Klippenstein ***@***.***> wrote:
The weird compilation error was due to the overly-general packagingOptions
exclusion. I reverted that, added only the ones it complained about, and
moved it into the single root build.gradle file so it's not duplicated
everywhere.
This seems to work, but a bunch of UI tests are flaking *extremely* hard,
so even if this PR goes green it might not be great to merge it yet.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#915?email_source=notifications&email_token=AAOMCHMUBPXAMD47MZ4VGKDRANVMXA5CNFSM4KLOQVT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKNBSLA#issuecomment-580524332>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOMCHKOHFSEBXM7P47EJ33RANVMXANCNFSM4KLOQVTQ>
.
|
So far they're fine on CI. But stop working, Ray. |
It's now:
Closes #833, #903.