From Fedora Project Wiki

(Created page with " {{Infobox_group | name = '''Toolbx''' | image = 300px|link=QA/Test Days | date = '''2024-03-27''' | time = all day | website = QA/Test Days | matrix = [https://matrix.to/#/#test-day:fedoraproject.org #test-day:fedoraproject.org] | irc = [irc://irc.libera.chat/#fedora-test-day #fedora-test-day] ([https://web.libera.chat/#fedora-test-day webirc]) | fedora_mailing_list = test }} {{admon/note | Can't make the date? | If you come to this pa...")
 
 
Line 58: Line 58:


== Test Results ==
== Test Results ==
=== Basic Test ===
{| class="wikitable" width=100%
! User
! Profile
! [http://fedoraproject.org/wiki/QA:Testcase_toolbox Basic]
! References
|-
| [[User:AngusVW|AngusVW]]
| Operating System: Fedora Linux 40 (Workstation Edition Prerelease) Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Latitude 7490
| {{result|pass}}<ref> Utilized toolbox version 0.0.99.5 on a bare metal Fedora 40 installation.
I did not understand how to execute release validating.
A new rootless toolbox container, fedora-toolbox-40, with default settings was created and verified.
A new rootfull toolbox container, ubuntu-toolbox-22.04, successfully created verified.
Both images/containers were listed with toolbox list and sudo toolbox list
Both containers were entered, packages were installed, and exited successfully</ref>
| <references/>
|-
| [[User:dtma|dtma]]
| KVM,F40 server,x86_64
| {{result|pass}}
| <references/>
|-
| [[User:ersen|ersen]]
| Fedora 40 x86_64 KVM
| {{result|pass}}
| <references/>
|-
| [[User:farribeiro|farribeiro]]
| F40 Silverbue
| {{result|pass}}
| <references/>
|-
| [[User:flyingfsck|flyingfsck]]
|
| {{result|pass}}<ref>Fedora 40 VM on Fedora 39. All toolbox tests passed</ref>
| <references/>
|-
| [[User:geraldosimiao|geraldosimiao]]
| F40 KDE at Acer Aspire V3-571 / i7-3632QM
| {{result|pass}}<ref>toolbox-0.0.99.5-8.fc40.x86_64</ref>
| <references/>
|-
| [[User:hricky|hricky]]
| F40 Silverbue, Bare Metal
| {{result|warn}}<ref>The optional (validation check) `skopeo copy` command returns an error due to a wrong transport definition.</ref>
| <references/>
|-
| [[User:nixuser|nixuser]]
| toolbox-0.0.99.5-8.fc40.x86_64 ~ Dell Precision T5610 2 x Intel(R) Xeon(R) CPU E5-2603 v2 @ 1.80GHz (8 cores total) NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1)
| {{result|fail}}<ref>It seems having VirtualBox installed and being a member of vboxusers causes toolbox to fail due to "If a user is a member of any group that grants access to device nodes in folders that have 750 permissions, all toolboxes can no longer be entered".  The upstream bug is https://github.com/containers/toolbox/issues/1348</ref>
| <references/>
|-
| [[User:plugs|plugs]]
| fedora_MATE
| {{result|pass}}<ref>It was a bit slow installing packages and I had to reboot a few times, using virt manager</ref>
| <references/>
|-
| [[User:pnemade|pnemade]]
| F40 Silverblue x86_64
| {{result|pass}}
| <references/>
|-
| [[User:r0b0ty|r0b0ty]]
|
| {{result|pass}}<ref>Using Fedora-KDE-Live-x86_64-40_Beta-1.10.iso in Virtual Machine, all expected results listed were observed.  No errors or anomalies to report.</ref>
| <references/>
|-
| [[User:vishalvvr|vishalvvr]]
|  KVM,F40,x86_64
| {{result|pass}}
| <references/>
|-
|}


The test results will be updates once the test day is over
[[Category:Fedora 40 Test Days]]
[[Category:Fedora 40 Test Days]]

Latest revision as of 02:25, 24 April 2024

Toolbx

Date 2024-03-27
Time all day

Website QA/Test Days
Matrix #test-day:fedoraproject.org
IRC #fedora-test-day (webirc)
Mailing list test


Can't make the date?
If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?[edit]

This Test Day will focus on Toolbx

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:

You can chat with us on Matrix or IRC. See the infobox on top of the page to learn where to join.

Prerequisite for Test Day[edit]

  • A virtual machine or a bare metal machine
  • An installation of Fedora 40 (any Edition or Spin). Make sure to fully update your system. If installing a fresh system, it's recommended to use the latest nightly image.

How to test?[edit]

Visit the results page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.

Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases.

Reporting bugs[edit]

Perhaps you've found an already-reported bug. Please look at:

All new bugs should be reported into the upstream bug tracker. A less-preferred alternative is to file them into Red Hat Bugzilla, in most cases against the toolbox component.

We really need bug reports!
Please note that just mentioning your problem into the comments section on the results page is not very helpful. Very often those problems only happen in specific circumstances, or with specific steps taken. We need the logs and screenshots, and we need to be able to ask you followup questions. Please file bug reports, it's much more useful than a short comment. Thank you!

When filing the bug, it's very helpful to include:

  • exact steps you've performed (and whether you can reproduce it again)
  • screenshots or videos, if applicable
  • system journal (log), which you can retrieve by journalctl -b > journal.txt
  • all output in a terminal, if started from a terminal
  • your system description

If you are unsure about exactly how to file the report or what other information to include, just ask us.

Please make sure to link to the bug when submitting your test result, thanks!

Test Results[edit]

Basic Test[edit]

User Profile Basic References
AngusVW Operating System: Fedora Linux 40 (Workstation Edition Prerelease) Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Latitude 7490
Pass pass
[1]
  1. Utilized toolbox version 0.0.99.5 on a bare metal Fedora 40 installation. I did not understand how to execute release validating. A new rootless toolbox container, fedora-toolbox-40, with default settings was created and verified. A new rootfull toolbox container, ubuntu-toolbox-22.04, successfully created verified. Both images/containers were listed with toolbox list and sudo toolbox list Both containers were entered, packages were installed, and exited successfully
dtma KVM,F40 server,x86_64
Pass pass
ersen Fedora 40 x86_64 KVM
Pass pass
farribeiro F40 Silverbue
Pass pass
flyingfsck
Pass pass
[1]
  1. Fedora 40 VM on Fedora 39. All toolbox tests passed
geraldosimiao F40 KDE at Acer Aspire V3-571 / i7-3632QM
Pass pass
[1]
  1. toolbox-0.0.99.5-8.fc40.x86_64
hricky F40 Silverbue, Bare Metal
Warning warn
[1]
  1. The optional (validation check) skopeo copy command returns an error due to a wrong transport definition.
nixuser toolbox-0.0.99.5-8.fc40.x86_64 ~ Dell Precision T5610 2 x Intel(R) Xeon(R) CPU E5-2603 v2 @ 1.80GHz (8 cores total) NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1)
Fail fail
[1]
  1. It seems having VirtualBox installed and being a member of vboxusers causes toolbox to fail due to "If a user is a member of any group that grants access to device nodes in folders that have 750 permissions, all toolboxes can no longer be entered". The upstream bug is https://github.com/containers/toolbox/issues/1348
plugs fedora_MATE
Pass pass
[1]
  1. It was a bit slow installing packages and I had to reboot a few times, using virt manager
pnemade F40 Silverblue x86_64
Pass pass
r0b0ty
Pass pass
[1]
  1. Using Fedora-KDE-Live-x86_64-40_Beta-1.10.iso in Virtual Machine, all expected results listed were observed. No errors or anomalies to report.
vishalvvr KVM,F40,x86_64
Pass pass