Skip to content
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

Bump agp from 8.7.1 to 8.7.2 #186

Merged
merged 1 commit into from
Nov 4, 2024

Bump agp from 8.7.1 to 8.7.2

2317ecb
Select commit
Loading
Failed to load commit list.
Sign in for the full log view
Merged

Bump agp from 8.7.1 to 8.7.2 #186

Bump agp from 8.7.1 to 8.7.2
2317ecb
Select commit
Loading
Failed to load commit list.
GitHub Actions / Test Results succeeded Nov 4, 2024 in 0s

16 tests ✅ passed, checks: ⚠️ 2

Test Suites ✅ 16 passed 🟡 0 skipped ❌ 0 failed ⌛ took
✅ com.example.login.ExampleUnitTest
  • ✅ addition_isCorrect (⌛ 0.002)
1 0 0 0.002
✅ com.example.login.ExampleUnitTest
  • ✅ addition_isCorrect (⌛ 0.003)
1 0 0 0.003
✅ com.example.login.ui.data.LoginDataSourceTest
  • ✅ testLogin (⌛ 0.007)
1 0 0 0.007
✅ com.example.login.ui.data.LoginDataSourceTest
  • ✅ testLogin (⌛ 0.018)
1 0 0 0.018
✅ com.example.myapplication.ExampleInstrumentedTest
  • ✅ useAppContext (⌛ 0.011)
1 0 0 4.959
✅ com.example.myapplication.ExampleUnitTest
  • ✅ addition_isCorrect (⌛ 0.019)
1 0 0 0.019
✅ com.example.myapplication.ExampleUnitTest
  • ✅ addition_isCorrect (⌛ 0.003)
1 0 0 0.003
✅ com.example.myapplication.ExampleUnitTest
  • ✅ addition_isCorrect (⌛ 0.003)
1 0 0 0.003
✅ com.example.myapplication.ExampleUnitTest
  • ✅ addition_isCorrect (⌛ 0.019)
1 0 0 0.019
✅ com.example.myapplication.MainActivityTest
  • ✅ shouldStart (⌛ 21.156)
1 0 0 21.156
✅ com.example.myapplication.MainActivityTest
  • ✅ shouldStart (⌛ 16.827)
1 0 0 16.827
✅ com.example.myapplication.MainActivityTest
  • ✅ shouldStart (⌛ 22.062)
1 0 0 22.062
✅ com.example.myapplication.MainActivityTest
  • ✅ shouldStart (⌛ 16.659)
1 0 0 16.659
✅ io.github.gmazzo.android.test.aggregation.AndroidTestCoverageAggregationPluginTest
  • ✅ applies correctly on a multi module project() (⌛ 8.848)
1 0 0 8.848
✅ io.github.gmazzo.android.test.aggregation.AndroidTestResultsAggregationPluginTest
  • ✅ applies correctly on a multi module project() (⌛ 0.626)
1 0 0 0.626
✅ MyUseCaseTest
  • ✅ testIsDone (⌛ 0.008)
1 0 0 0.008
Android Lint 🛑 0 errors ⚠️ 2 warnings 💡 0 others
Lint / ObsoleteLintCustomCheck 0 2 0

Annotations

Check warning on line 0 in /home/runner/work/gradle-android-test-aggregation-plugin/gradle-android-test-aggregation-plugin/demo-project/app/build/intermediates/lint-cache/lintReportProdDebug/migrated-jars/androidx.navigation.common.lint.NavigationCommonIssueRegistry-5daa12651be0734e..jar

See this annotation in the file changed.

@github-actions github-actions / Test Results

Lint: Obsolete custom lint check

Library lint checks out of date;
these checks **will be skipped**!

Lint found an issue registry (`androidx.navigation.common.lint.NavigationCommonIssueRegistry`)
which was compiled against an older version of lint
than this one. This is usually fine, but not in this
case; some basic verification shows that the lint
check jar references (for example) the following API
which is no longer valid in this version of lint:
org.jetbrains.kotlin.analysis.api.lifetime.KaDefaultLifetimeTokenProvider#Companion
(Referenced from androidx/navigation/lint/UtilKt.class)

Therefore, this lint check library is **not** included
in analysis. This affects the following lint checks:
`EmptyNavDeepLink`,`WrongStartDestinationType`,`MissingSerializableAnnotation`,`MissingKeepAnnotation`

Recompile the checks against the latest version, or if
this is a check bundled with a third-party library, see
if there is a more recent version available.

Version of Lint API this lint check is using is 14.
The Lint API version currently running is 16 (8.7+).
Raw output
Lint can be extended with "custom checks": additional checks implemented by developers and libraries to for example enforce specific API usages required by a library or a company coding style guideline.

The Lint APIs are not yet stable, so these checks may either cause a performance degradation, or stop working, or provide wrong results.

This warning flags custom lint checks that are found to be using obsolete APIs and will need to be updated to run in the current lint environment.

It may also flag issues found to be using a **newer** version of the API, meaning that you need to use a newer version of lint (or Android Studio or Gradle plugin etc) to work with these checks.

Check warning on line 0 in /home/runner/work/gradle-android-test-aggregation-plugin/gradle-android-test-aggregation-plugin/demo-project/app/build/intermediates/lint-cache/lintReportProdDebug/migrated-jars/androidx.navigation.runtime.lint.NavigationRuntimeIssueRegistry-a8fea42aedb9bdb3..jar

See this annotation in the file changed.

@github-actions github-actions / Test Results

Lint: Obsolete custom lint check

Library lint checks out of date;
these checks **will be skipped**!

Lint found an issue registry (`androidx.navigation.runtime.lint.NavigationRuntimeIssueRegistry`)
which was compiled against an older version of lint
than this one. This is usually fine, but not in this
case; some basic verification shows that the lint
check jar references (for example) the following API
which is no longer valid in this version of lint:
org.jetbrains.kotlin.analysis.api.lifetime.KaDefaultLifetimeTokenProvider#Companion
(Referenced from androidx/navigation/lint/UtilKt.class)

Therefore, this lint check library is **not** included
in analysis. This affects the following lint checks:
`DeepLinkInActivityDestination`,`WrongStartDestinationType`,`WrongNavigateRouteType`,`MissingKeepAnnotation`,`MissingSerializableAnnotation`

Recompile the checks against the latest version, or if
this is a check bundled with a third-party library, see
if there is a more recent version available.

Version of Lint API this lint check is using is 14.
The Lint API version currently running is 16 (8.7+).
Raw output
Lint can be extended with "custom checks": additional checks implemented by developers and libraries to for example enforce specific API usages required by a library or a company coding style guideline.

The Lint APIs are not yet stable, so these checks may either cause a performance degradation, or stop working, or provide wrong results.

This warning flags custom lint checks that are found to be using obsolete APIs and will need to be updated to run in the current lint environment.

It may also flag issues found to be using a **newer** version of the API, meaning that you need to use a newer version of lint (or Android Studio or Gradle plugin etc) to work with these checks.