New version of Robolectric 4.9.x

[sebastienrussell]

Hello @utzcoz

I just wanna ask when is suppose to be the next release of Robolectric so the proxy settings stuff are available to my team?

Or can I already have access to a snapshot version?

I'm just asking so we can organise ourselves not to rush you guys to release something 😄

Have a nice day.

[alwa]

It would also feel re-assuring if the latest release uses stable dependencies, https://github.com/robolectric/robolectric/pull/7785/files

[hoisie]

I can do a new minor release if there is demand.

[sebastienrussell]

Yes, we would benefit from a minor release.

[utzcoz]

@hoisie I will add some PRs/fixes that I want to be released at next minor release later.

[utzcoz]

@hoisie Full list here:

1. Bump ASM to 9.4 #7823 Bump ASM to 9.4
2. Add shadow for LocaleManager#getSystemLocales #7804 Add shadow for LocaleManager#getSystemLocales
3. Update to androidx.test 11.04.2022 stable release #7785 Update to androidx.test 11.04.2022 stable release
4. Use uninterruptibly acquire for ResTable's lock #7761 Use uninterruptibly acquire for ResTable's lock
5. fix: Avoid referring to Android S's TelephonyCallback #7786 fix: Avoid referring to Android S's TelephonyCallback

[utzcoz]

I also want #7859 if it can be merged before 4.9.1 release.

[hoisie]

OK I cherry-picked some commits to the 4.9.x branch:

https://github.com/robolectric/robolectric/commits/robolectric-4.9.x

Let me know if anything is missing.

I was not able to cleanly cherry-pick the Update to androidx.test 11.04.2022 stable release. It seems there has been a ton of changes to dependencies.gradle that are intertwined with a lot of other changes to build.gradle files, so I am not comfortable cherry-picking everything.

cc @brettchabot , but I believe the versioning scheme of androidx.test and espresso are pretty much arbitrary. Every commit is tested on all of Google's tests, so each commit should be very stable. Even alpha releases are just as stable as 'stable' releases.

[utzcoz]

I also want this one #7859.
@hoisie Before cherry-picking the PR to bump AGP to stable version, it's needed to cherry-pick this PR created by @brettchabot: #7683.

[utzcoz]

I cherry-picked related commits for axt versions at #7876. @hoisie You can cherry-pick them to 4.9.x after testing. There are some conflicts when cherry-picking, @brettchabot could you help to give a look at these commits? Thanks.

[hoisie]

If the axt version bumps do not solve specific, tangible issues it is not worth trying to cherry-pick them. We can wait for 4.10.

Like I mentioned before, the axt libraries are developed in a continuous fashion using blaze/bazel, and this versioning approach does not map cleanly to maven versioning. There difference between an alpha/beta/stable release is insignificant, in my opinion.

[utzcoz]

IMO, I don't think it is necessary to update AXT version for 4.9.1, but there are some developers/users want it. I agree with AXT's master/main head strategy for development and am confident with the stability of alpha AXT, but as you said, the alpha/rc/stable version naming might raise confusions to developers/users. I agree with to leave it to 4.10, and cc @alwa for our consideration.

[brettchabot]

You are both correct of course that androidx.test basically follows head strategy for development, and 'alpha' releases from a functional perspective should be quite stable. However, occasionally between alpha and stable there can be fixes for issues discovered by gradle/maven users as well as API cleanup.

However, Robolectric largely only uses androidx.test for its tests, and only depends on androidx.test:monitor and espresso idling resource for its released artifacts. Looking through the release notes I agree with Michael that there doesn't seem to be any changes that are critical to pick up in 4.9.x

[hoisie]

Actually I managed to find a reasonably small subset of CPs that allows AndroidX Test version updates, so these will be included with 4.9.1

[utzcoz]

I found another issue we need to upgrade AXT version to fix it on 4.9.1: #7669.

[hoisie]

I'm preparing a release for this branch:

https://github.com/robolectric/robolectric/commits/robolectric-4.9.x

[hoisie]

Just released https://github.com/robolectric/robolectric/releases/tag/robolectric-4.9.1

(it may take a few minutes to propagate...)

[sebastienrussell]

Thanks @hoisie @utzcoz @brettchabot for this minor version of Robolectric
You've just helped ~20 Android devs on my team.

Continue the good work 🥳

[utzcoz]

@hoisie As we discussed at #7881, we might need a 4.9.2 release with these patches:

1. Rebuild nativeruntime so files with Ubuntu 18.04 for Linux to reduce potential higher glibc version dependency. cc @ZSmallX .
2. Ensure ShadowSpeechRecognizer can work with SDK 28: Ensure ShadowSpeechRecognizer can work with SDK 28 #7859.
3. Add call to $$robo$init for Jacoco-instrumented constructors : Add call to $$robo$init for Jacoco-instrumented constructors #7677. cc @ZSmallX .

[hoisie]

Sounds good @utzcoz. Will start the process.

[hoisie]

4.9.2 has been released.

[alwa]

I noticed a regression, or at least changed behavior, in 4.9.1 and 4.9.2 compared to 4.9. It's reported here: #7900

[mreichelt]

@utzcoz As described over at #6803 (comment), we'd love to try the changes to ShadowBluetoothGatt: a794679

[utzcoz]

Hi @hoisie , could you help do a minor 4.9.3 release? If anyone has other commits that want to be merged into 4.9.3, please post as comments for this thread.

[hoisie]

Let's just do 4.10-alpha-1. There will be some kinks to work out with native graphics, so we may as well start the 4.10 process.

[utzcoz]

Sounds great. cc @mreichelt .