2020-10-21 Moblab Update: ChromeOS Update, Remote Console**To intake this update, please find the update button on the new UI here. This change will require a reboot to be applied. Please wait until all tests are complete before applying this change. This change includes revisions to the new UI which may require a cache clear to be seen.** This update includes an update to the underlying moblab ChromeOS version; after the update you will be running version R86-13421.72.0 This update also introduces remote console functionality, which allows more Moblab/DUT information to be uploaded and summarized in CPCon ( additional information in the link above ). Instructions on how to enable the remote console can be found here. Bugfixes: Fix to run-suite page occasionally not starting suite + not showing error. - https://crbug.com/1137063 Fix to run-suite page to only show compatible build target or model selection. - https://crbug.com/1137063 Fix so that OAuth credentials are refreshed on configuration changes. - https://crbug.com/1136552 OS Recovery ImageOctober 14th 2020An update was pushed to fix a problem where DUT would get stuck in "Provisioning" state. If you are not experiencing this problem Please update your Moblab when it is next not running tests by pressing the Update button. If you have already have DUT's stuck in "Provisioning" the most efficient way to proceed is to powerwash the Moblab that will guarantee you have the latest software and also reset the stuck DUT's. September 28th 2020**To intake this update, please find the update button on the new UI here ( or update via the old UI ). This change should not require a reboot to be applied. This change includes revisions to the new UI which may require a cache clear to be seen.** This update is intended to address user issues running memory qual; particularly problems associated with bug and part ID being missing during suite execution. This update also introduces changes to the run suite UI. After update, users should be able to see a slightly different run-suite page ( old vs new - if this change is not seen, try to clear the cache of your Moblab ). August 18th 2020**To intake this update, please find the update button on the new UI here ( or update via the old UI ). This change will require a reboot to be fully applied** This update is intended to address user issues running storage qual. The recommendation up until this point for those urgently blocked on storage qual failures was to revert to the R78 version of Moblab. With this update, storage qual tests should run successfully on fully up-to-date Moblabs ( R83-13020.65.0 , with all updates pulled in ). August 7th 2020 **To intake this update, please find the update button on the new UI here ( or update via the old UI ). This change will require a reboot to be fully applied** This update does not have an UI or functionality changes. There are several minor backend changes that are meant to improve Moblab's ability to keep itself up-to-date. This update may be useful if you are experiencing issues with Moblab's not fully taking in new changes (i.e., docker containers not fully updating ). July 16th 2020**To intake this update, please find the update button on the new UI here ( or update via the old UI ). This change will require a reboot to be fully applied** This release includes a few additional fixes to both the new UI and generally. It also sets the new UI as default (that is, it will be on ‘localhost’). The old UI will still be available ( accessible via a link on the upper-right: instructions ). Please find instructions for Moblab operations on the new UI here. If you encounter any issues, please submit feedback. This will help us improve the new UI to fully replace the old UI, which will be removed shortly. --------------------------------------------------- *Note that if you are doing port-forwarding to use Moblab remotely, you will have to port-forward to from your machine’s 6001 port to the Moblab 6001 port ( in addition to forwarding a port on your machine to the Moblab’s 80 port ). July 12th 2020Moblab software has been updated to fix some bugs/make improvements. https://crbug.com/1099818 Fix a bug where is rare circumstances you could get an error message after bootup that says "Table definition has changed, please retry transaction" https://crbug.com/1098932 Fix an issue in the offloader where if the file permissions were incorrectly set the offloader would crash. At the same time some other fixes were make to offloader to work in situations where the network had/dropped out / rejected connections for some period of time. Another issue was fixed that did not have a bug filed that caused logging message internal to moblab not be be cleaned up correctly and so used more disk than necessary. For this update the Moblab needs a reboot. When your moblab is next not running any tests please reboot the moblab and it will automatically pick up the latest version of the software.  This link directs to a new, replacement UI for running suites from Moblab. This UI will eventually become the default and then only UI available on Moblab. It is recommended that users attempt to run their suites from this UI as soon as possible, to smoothen the eventual forced transition to the new UI. If you do not see the link pictured above to the new UI, verify that you are on a Moblab with version R83-13020.65.0 or newer, if your Moblab is older, please read the following to update: https://chromium-review.googlesource.com/c/chromiumos/platform/moblab/+/2269145 If you are on a Moblab of version R83-13020.65.0 or newer and still do not see the above link, please reach out to me or comment. June 11th 2020Moblab software has had an update to fix two bugs:Results offloader is not removing results from the local disk after 4 days. Adding some devices in Manage DUT caused label errors https://crbug.com/1093212There is no longer a change to the ChromeOS version on update - you should see a message "Moblab software update available"  When there are no pending or running tests on the moblab you can just press the update button, the update should take about 3-5 minutes. If you are uncertain at any time your moblab has the latest software, a reboot of the device will always check and download any updates needed. June 3rd 2020: Release R83-13020.65.0ALERT - THIS UPDATE WILL POWERWASH YOUR MOBLAB REMOVING ALL DATA FROM IT HAVE YOUR BOTO KEY AND SECRET READY BEFORE UPDATING. IF YOU HAVE MULTIPLE MOBLAB WE RECOMMEND UPDATING JUST ONE MOBLAB AND VERIFYING IT WORKS BEFORE UPDATING THE OTHER DEVICES IN YOUR LAB. We are making a significant change to the way the moblab software is configured and released. Longer term this is going to mean quicker less disruptive changes to the moblab and the ability of the Google team to spend more time adding features rather than maintaining and releasing the existing code. However for this update we need to delete everything and start again, that is why the automatic powerwash was implemented. As a user initially you will not see much change to how the moblab works - this is intentional. It is easier for users to find issues with our big change if they are familiar with the UI and how things work. Later we will make other changes to the UI and add more functionality. This will be announced as it comes out. However what you might notice: * On first bootup the moblab will be slow for the Autotest UI to show. Moblab is downloading the software now on first boot, this is about 4GB of data so depending on your connection it may take 2-5 minutes. The software is cached on disk so subsequent bootup should not be so slow. * We have removed WMatrix, it was not working correctly and no one was complaining so it was deleted. * There is a new button on Mobmonitor called "Send Logs" this copies logs to your google cloud bucket. It is very helpful if you press that button before you report an issue to Google, we can find the logs and not have to ask you to send them by email. * Direct SSH into the device has been removed, you can still SSH into a sandbox that allows you to forward the UI over SSH and see logs but you do not have direct access to the machine this way. |
|
|