Fixed
Status Update
Comments
je...@google.com <je...@google.com>
da...@google.com <da...@google.com>
ma...@google.com <ma...@google.com> #2
The fix for this issue will be available in 4.1 beta 4, when double clicking on a NULL cell the NULL value will be persisted.
The drawback of this solution is that it's not possible to just edit a cell and replace NULL with empty string. It has to be done by running an UPDATE query or editing the cell to something different from empty string first.
pr...@google.com <pr...@google.com> #3
@daniellabar checking on this
da...@google.com <da...@google.com>
ma...@google.com <ma...@google.com> #4
Could you please post here what was the issue?
va...@google.com <va...@google.com> #5
ma...@google.com <ma...@google.com> #6
Thank you for the update and for fixing it!
zo...@gmail.com <zo...@gmail.com> #7
Hi there, I am seeing the "Computer Architecture Environment not initialized properly." error on my end when using a GMD test device. I am using AGP 8.1.4.
I am testing out a new Jenkins installation and running my tests from a Jenkins job, FWIW. Periodically I get stuck in cases where running my Android instrumentation tests on a gradle managed device (Pixel 4a, API 33, aosp-atd) results in this error being encountered. I am not sure how I get into that case (the device works well some of the time), nor do I know how I get this resolved (I restart the computer, create a different named device, etc and sometimes that works). But very quickly the issue comes back.
I found this post and tested out the suggested workaround involving `com.android.utils.Environment.initialize()` being added - and so far this is working in my testing.
Is this issue still in the wild? I see the issue is marked as fixed here, but is there a particular release/fix version this issue was resolved in? Verified In/Targeted To fields are blank as well, and In Prod toggle is off, but the status is Fixed!
I am testing out a new Jenkins installation and running my tests from a Jenkins job, FWIW. Periodically I get stuck in cases where running my Android instrumentation tests on a gradle managed device (Pixel 4a, API 33, aosp-atd) results in this error being encountered. I am not sure how I get into that case (the device works well some of the time), nor do I know how I get this resolved (I restart the computer, create a different named device, etc and sometimes that works). But very quickly the issue comes back.
I found this post and tested out the suggested workaround involving `com.android.utils.Environment.initialize()` being added - and so far this is working in my testing.
Is this issue still in the wild? I see the issue is marked as fixed here, but is there a particular release/fix version this issue was resolved in? Verified In/Targeted To fields are blank as well, and In Prod toggle is off, but the status is Fixed!
hu...@google.com <hu...@google.com> #8
The "Computer Architecture Environment not initialized properly" error was fixed in AGP 8.2.0.
We've also worked on other stability issues related to the emulator snapshot, so I would recommend using the latest version if possible.
zo...@gmail.com <zo...@gmail.com> #9
Thank you for the speedy reply - I will check out AGP 8.2.0 as soon as I am able to.
zo...@gmail.com <zo...@gmail.com> #10
I was able to check out AGP 8.2.0, and I can confirm that it does seem more stable in this regard - thank you once more.
Description
When running ui test tasks from multiple project in the same run, sometimes it hangs permanently. The only option is to force stopping the execution with CTRL-C. At this point future executions will always fail with:
At this point it's necessary to clean to have the instrumentation test tasks for managed devices working again.
I've added a full stacktrace here: