canonical-ubuntu-qa team mailing list archive

[Adriano Cordova Fedeli <mp+488345@xxxxxxxxxxxxxxxxxx>]

Adriano Cordova Fedeli has proposed merging ~adrianoco/ubuntu-manual-tests:main into ubuntu-manual-tests:main.

Commit message:
Remove VisionFive2 and Milk-V Mars tests as they are part of JH7110 testing now.
Remove duplicated line in 1753_QEMU_riscv64_install

Requested reviews:
  Tim Andersson (andersson123)
  Heinrich Schuchardt (xypron)

For more details, see:
https://code.launchpad.net/~adrianoco/ubuntu-manual-tests/+git/ubuntu-manual-tests/+merge/488345
-- 
Your team Canonical's Ubuntu QA is subscribed to branch ubuntu-manual-tests:main.

diff --git a/testcases/image/1753_QEMU_riscv64_install b/testcases/image/1753_QEMU_riscv64_install
index b845111..d0fcb57 100644
--- a/testcases/image/1753_QEMU_riscv64_install
+++ b/testcases/image/1753_QEMU_riscv64_install
@@ -15,7 +15,6 @@ On your installed Ubuntu machine.
     -device virtio-net-device,netdev=net0 \
     -drive file=disk,format=raw,if=virtio \
     -drive file=<release>-live-server-riscv64.iso,format=raw,if=virtio,readonly=on \
-    -drive file=disk,format=raw,if=virtio \
     -device virtio-rng-pci
 </pre></dt>
     <dt>Install on the 16 GiB drive.</dt>
diff --git a/testcases/image/1780_Install VisionFive 2 b/testcases/image/1780_Install VisionFive 2
deleted file mode 100755
index 640df46..0000000
--- a/testcases/image/1780_Install VisionFive 2
+++ /dev/null
@@ -1,38 +0,0 @@
-The scope of this test is to ensure that riscv64+visionfive2 image boots from SD card on StarFive VisionFive 2 board
-
-<dl>
-    <dt>Flash downloaded image onto SD card</dt>
-        <dd>You can use Gnome Disks app to restore img.xz onto the SD card</dd>
-        <dd>Alternatively you can use xz -d to decompress, and then dd to copy the image to the SD card</dd>
-    <dt>Connect networking, serial console to the board</dt>
-        <dd>Ethernet cable for networking</dd>
-        <dd>FTDI adapter for serial console (pinout available here: https://rvspace.org/en/Product/VisionFive/Technical_Documents/VisionFive_Single_Board_Computer_Quick_Start_Guide)</dd>
-    <dt>Connect to the serial console</dt>
-        <dd>sudo screen /dev/ttyUSB0 115200</dd>
-    <dt>Power on the board</dt>
-        <dd>You should see U-BOOT output</dd>
-        <dd>It should then boot GRUB after a delay</dd>
-        <dd>You should see GRUB menu</dd>
-        <dd>It should then boot the default kernel after a delay</dd>
-        <dd>After a while cloud-init will run</dd>
-	<dd>Wait for the 'Cloud-init finished' message</dd>
-        <dd>Then one will be able to login</dd>
-    <dt>Login and change password</dt>
-        <dd>Login using ubuntu for both username and password</dd>
-        <dd>Reenter ubuntu password again</dd>
-        <dd>Set new password</dd>
-        <dd>Confirm the new password</dd>
-    <dt>Perform generic testing</dt>
-        <dd>Check that apt update works</dd>
-        <dd>Run any command that is not installed, check that command-not-found recommends things to install</dd>
-        <dd>e.g. hello</dd>
-        <dd>Install a package and check that it works, e.g. hello</dd>
-    <dt>Reboot</dt>
-        <dd>The board should reboot normally</dt>
-    <dt>Poweroff</dt>
-        <dd>Console messages should reach poweroff target</dd>
-        <dd>There should be final kernel dmsg powering off</dd>
-        <dd>Manually turn power-off from the board</dd>
-</dl>
-<strong>If all actions produce the expected results listed, please <a href="results#add_result">submit</a> a 'passed' result.
-    If an action fails, or produces an unexpected result, please <a href="results#add_result">submit</a> a 'failed' result and <a href="../../buginstructions">file a bug</a>. Please be sure to include the bug number when you <a href="results#add_result">submit</a> your result.</strong>
diff --git a/testcases/image/1795_Install Milk-V Mars b/testcases/image/1795_Install Milk-V Mars
deleted file mode 100755
index 5876f76..0000000
--- a/testcases/image/1795_Install Milk-V Mars
+++ /dev/null
@@ -1,38 +0,0 @@
-The scope of this test is to ensure that riscv64+visionfive2 image boots from SD card on Milk-V Mars board
-
-<dl>
-    <dt>Flash downloaded image onto SD card</dt>
-        <dd>You can use Gnome Disks app to restore img.xz onto the SD card</dd>
-        <dd>Alternatively you can use xz -d to decompress, and then dd to copy the image to the SD card</dd>
-    <dt>Connect networking, serial console to the board</dt>
-        <dd>Ethernet cable for networking</dd>
-        <dd>USB to TTL adapter for serial console (pinout available here: https://milkv.io/docs/mars/getting-started/setup)</dd>
-    <dt>Connect to the serial console</dt>
-        <dd>sudo screen /dev/ttyUSB0 115200</dd>
-    <dt>Power on the board</dt>
-        <dd>You should see U-BOOT output</dd>
-        <dd>It should then boot GRUB after a delay</dd>
-        <dd>You should see GRUB menu</dd>
-        <dd>It should then boot the default kernel after a delay</dd>
-        <dd>After a while cloud-init will run</dd>
-	<dd>Wait for the 'Cloud-init finished' message</dd>
-        <dd>Then one will be able to login</dd>
-    <dt>Login and change password</dt>
-        <dd>Login using ubuntu for both username and password</dd>
-        <dd>Reenter ubuntu password again</dd>
-        <dd>Set new password</dd>
-        <dd>Confirm the new password</dd>
-    <dt>Perform generic testing</dt>
-        <dd>Check that apt update works</dd>
-        <dd>Run any command that is not installed, check that command-not-found recommends things to install</dd>
-        <dd>e.g. hello</dd>
-        <dd>Install a package and check that it works, e.g. hello</dd>
-    <dt>Reboot</dt>
-        <dd>The board should reboot normally</dt>
-    <dt>Poweroff</dt>
-        <dd>Console messages should reach poweroff target</dd>
-        <dd>There should be final kernel dmsg powering off</dd>
-        <dd>Manually turn power-off from the board</dd>
-</dl>
-<strong>If all actions produce the expected results listed, please <a href="results#add_result">submit</a> a 'passed' result.
-    If an action fails, or produces an unexpected result, please <a href="results#add_result">submit</a> a 'failed' result and <a href="../../buginstructions">file a bug</a>. Please be sure to include the bug number when you <a href="results#add_result">submit</a> your result.</strong>