Skip to content

pages build and deployment #176

pages build and deployment

pages build and deployment #176

Triggered via dynamic April 4, 2026 14:04
Status Success
Total duration 39s
Artifacts 1

pages-build-deployment

on: dynamic
report-build-status
4s
report-build-status
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
MainInstrumentedTest.timeGraph: app/src/androidTest/kotlin/com/vrem/wifianalyzer/MainInstrumentedTest.kt#L50
androidx.test.espresso.NoMatchingViewException: No views in hierarchy found matching: (view.getId() is <16908314/android:id/button2> and (view has effective visibility <VISIBLE> and view.getGlobalVisibleRect() to return non-empty rectangle)) If the target view is not part of the view hierarchy, you may need to use Espresso.onData to load it from one of the following AdapterViews:android.widget.ExpandableListView{6ea1a94 VFED.VC.. ........ 0,0-996,1521 #7f09001c app:id/accessPointsView}
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/deploy-pages@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
github-pages Expired
2.6 MB
sha256:eaf03bd4607fe4fa34fe4e54e0edb00a9fcc69f05e30fd3d0ee1e671457efabd