mlcommons
Release 5.0.2
For 5.0.2 release, we need Update Release Notes Run full Browser Stack CI/CD coverage test Release notes should be part of the App?
Anything else?
- The Browser Stack test is already run automatically when merged into the master branch.
- I think the release note should not be included in the app; else, we need a PR for any change. There is an extra section for it in the Play Store, and in GitHub, we can add it to the release description.
@anhappdev he Browser Stack test is already run automatically when merged into the master branch.
Since this PR is already merged, https://github.com/mlcommons/mobile_app_open/pull/1049, did the full BrowserSTack CI/CD (expanded one) pass? then we only need update the https://github.com/mlcommons/mobile_app_open/blob/master/flutter/assets/text/about.md with new SOC supported (Exynos 2500)?
Yes. The extended test passed: https://github.com/mlcommons/mobile_app_open/actions/runs/17875525054
Shall we use this commit for the release? https://github.com/mlcommons/mobile_app_open/commit/0e726d86f125515ddfde62c3f72f6b71c96ac804
Shall we use this commit for the release? 0e726d8
Yes, it should be the latest version with the correct app version. In that case, please also test the corresponding build. android-apk-unified-579
I agree with Anh that the releases notes can go into the Play Store and GitHub listings and don't need to be embedded in the app.
For this release, what should we say. I think it's just "Adds support for Samsung <what product names?>" Right?
Any other changes?
Shall we use this commit for the release? 0e726d8
Yes, it should be the latest version with the correct app version. In that case, please also test the corresponding build. android-apk-unified-579
Tested it with the FLIP 7 and works as expected.
I agree with Anh that the releases notes can go into the Play Store and GitHub listings and don't need to be embedded in the app.
For this release, what should we say. I think it's just "Adds support for Samsung <what product names?>" Right?
Any other changes?
Release on Github and release note looks good to me to publish on PlayStore, Thanks!
Shall we use this commit for the release? 0e726d8
Yes, it should be the latest version with the correct app version. In that case, please also test the corresponding build. android-apk-unified-579
Tested it with the FLIP 7 and works as expected.
I tried testing on flip 7. But there was quite a bit of run to run variation. Also the difference between the quick run and the performance mode is quite high.
There is also quite a bit of gap with the submitted numbers as well.
https://github.com/mlcommons/submissions_mobile_v5.0/blob/Samsung/closed/Samsung/results/exynos2500/Performance.jpg
Do we need to enable any specific settings in the phone?
@mohitmundhragithub thanks for checking, this is also our observation, I dont know of any special setting, but SW Android updates may vary the result, due to thermal control which makes the result of the very long run dependent on the temperature and ambient ventilation. The results of the quick run seems much more consistent as it finishes in less than 10 minutes, here is a quick run I got yesterday from the app @mohitmundhragithub for SOC Integration there is no official publication, so variation in results from different users is something to be expected
@Mostelk FYI, it was updated on the Play Store. https://play.google.com/store/apps/details?id=org.mlcommons.android.mlperfbench&hl=en
@anhappdev @freedomtan The PlayStore version is crashing on FLIP 7 but the released 5.0.2 version is working fine, looks there is some problem with PlayStore as we had before?
@anhappdev @mohitmundhragithub I just tested the Play Store App on S23 Ultra as well with Snapdragon backend, it also crashed once GO is pressed.
@Mostelk Do you have a crash report or log? Also, what is the Android version on those devices?