June 5th, 2019: Release R75-12105.116.0
This release is available for Wukong devices only.
This release is just part of the regular scheduled updates.
Fixes:
- Fixed issues in mobmonitor showing incorrect hearbeat warnings.
- Fixed issue in Manage DUT where the UI incorrectly claimed it could not SSH into the DUT.
- Fixed issue in LXC install packages, conflicts with old version of pip tool.
- Updated moblab container base image to version 09, contents are updated to latest version and it should be smaller in size.
It is recommend using auto-update for this and all future releases. The "Moblab Admin" page has the current version your moblab is running
along with a button to update to a new version if available.
Before you update wait until all tests are complete on that device. Updates require reboots and running tests will be aborted in the reboot.
June 5th, 2019: Release R74-11895.134.0
**** R74 WILL BE THE LAST GUADO MOBLAB MILESTONE ********
This release is just part of the regular scheduled updates.
If fixes one issue that a few partners have experienced with running tests on some ARM platforms.
It is recommend using auto-update for this and all future releases. The "Moblab Admin" page has the current version your moblab is running
along with a button to update to a new version if available.
Before you update wait until all tests are complete on that device. Updates require reboots and running tests will be aborted in the reboot.
If you need a recovery image for this version contact your regular google support or email moblab-discuss@chromium.org
Apr 26th, 2019: Release R73-11647.175.0
This push is a regular maintenance update
There is one bug fix to address problems at moblab boot time if the DHCP server is very slow at giving
the moblab an IP address. In this case the moblab can get confused as to what is the intranet NIC port vs the internet NIC port.
It is recommend using auto-update for this and all future releases. The "Moblab Admin" page has the current version your moblab is running
along with a button to update to a new version if available.
Before you update wait until all tests are complete on that device. Updates require reboots and running tests will be aborted in the reboot.
If you need a recovery image for this version contact your regular google support or email moblab-discuss@chromium.org
Mar 12th, 2019: Release R72-11316.178.0
When provisioning some newer R74/R75 images the provision will fail, and the logs will have an error like
File "/usr/lib/devserver/build_artifact.py", line 247, in _UpdateName
raise ArtifactDownloadError('Too many artifacts match %s' % self.name)
ArtifactDownloadError: Too many artifacts match *_full_*
It is recommend using auto-update for this and all future releases. The "Moblab Admin" page has the current version your moblab is running
along with a button to update to a new version if available.
Before you update wait until all tests are complete on that device. Updates require reboots and running tests will be aborted in the reboot.
If you need a recovery image for this version contact your regular google support or email moblab-discuss@chromium.org
Feb 22nd, 2019: Release R72-11316.154.0
There are no visible user changes, there is one change to the test server packaging which if not updated could cause some CTS tests to fail
with a message like "No module named lxml"
There are some other bug fixes and small version updates also.
It is recommend using auto-update for this and all future releases. The "Moblab Admin" page has the current version your moblab is running
along with a button to update to a new version if available.
Before you update wait until all tests are complete on that device. Updates require reboots and running tests will be aborted in the reboot.
Oct 24th, 2018: Release R69-10895.90.0
No major changes in functionality, we continue to work to make moblab faster and more reliable.
Fixed an issue with gs_offloader (process that copies results to cloud storage) should reduce disk usage and improve performance of moblab.
Extended the time that DUT builds are cached on the device, fix necessary for long running component
qualification tests but might increase disk usage on external drive.
For storage qual and memory qual you are now required to provide a bug number and part number when the test is started
If you are running Disk Qualification tests you must use a R69 or newer DUT build, if you are uncertain please
contact your google representative before you start the test.
It is recommend using auto-update for this and all future releases, you can see the version of moblab you are running and do an upgrade
on the "Moblab Admin" default page " http://<moblab_ip>/moblab_setup/#tab_id=config_Wizard
