#2442 Automate test TestInstanceNodeWithPbr - #2443

🖼️ Screenshot tests have failed.

The purpose of these tests is to ensure that changes introduced in this PR don't break visual features. They are visual unit tests.

📄 Where to find the report:

• Go to the (failed run) > Summary > Artifacts > screenshot-test-report
• Download the zip and open jme3-screenshot-tests/build/reports/ScreenshotDiffReport.html

⚠️ If you didn't expect to change anything visual:
Fix your changes so the screenshot tests pass.

✅ If you did mean to change things:
Review the replacement images in jme3-screenshot-tests/build/changed-images to make sure they really are improvements and then replace and commit the replacement images at jme3-screenshot-tests/src/test/resources.

✨ If you are creating entirely new tests:
Find the new images in jme3-screenshot-tests/build/changed-images and commit the new images at jme3-screenshot-tests/src/test/resources.

Note; it is very important that the committed reference images are created on the build pipeline, locally created images are not reliable. Similarly tests will fail locally but you can look at the report to check they are "visually similar".

See https://github.com/jMonkeyEngine/jmonkeyengine/blob/master/jme3-screenshot-tests/README.md for more information

Strange, this PR said that it had passed all checks.

However after I merged it, I got a notification saying that the master branch build failed: https://github.com/jMonkeyEngine/jmonkeyengine/actions/runs/15092754471/job/42423482622#step:5:113

It looks like that log says:

`FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':jme3-android-native:downloadStbImage'.
> Can't get https://raw.githubusercontent.com/jMonkeyEngine/stb/0224a44a10564a214595797b4c88323f79a5f934/stb_image.h to /__w/jmonkeyengine/jmonkeyengine/jme3-android-native/build/decode/stb_image.h

@stephengold @riccardobl do either of you know what this build failure indicates?

It has to do with building natives for Android.

Likely it's a transient network issue, in which case the job might succeed if you retry it.

the job might succeed if you retry it.

Thanks, I re-ran the build and that resolved everything.