Comments (7)
PraveenPenguin
commented on September 16, 2024
@vrbagalkote can you please have a look in to this issue ?
from avocado-misc-tests.
vrbagalkote
commented on September 16, 2024
@naveedus Can you please attach job.log file.
from avocado-misc-tests.
naveedus
commented on September 16, 2024
from avocado-misc-tests.
PraveenPenguin
commented on September 16, 2024
@naveedus are you not facing this any more please suggest ?
from avocado-misc-tests.
naveedus
commented on September 16, 2024
I uploaded the job log and closed this by mistake..
reopening the issue.
from avocado-misc-tests.
narasimhan-v
commented on September 16, 2024
The issue here is:
2017-04-24 06:05:19,813 process L0389 INFO | Running 'echo 'yes' | mdadm --create --verbose --assume-clean /dev/md/mdsraid --level=1 --raid-devices=1 /dev/dm-5 --spare-devices=1 /dev/dm-6 --force'
2017-04-24 06:05:19,818 process L0479 DEBUG| [stderr] mdadm: /dev/dm-5 appears to be part of a raid array:
2017-04-24 06:05:19,819 process L0499 INFO | Command 'echo 'yes' | mdadm --create --verbose --assume-clean /dev/md/mdsraid --level=1 --raid-devices=1 /dev/dm-5 --spare-devices=1 /dev/dm-6 --force' finished with 1 after 0.00364995002747s
2017-04-24 06:05:19,819 process L0479 DEBUG| [stderr] level=raid0 devices=2 ctime=Mon Apr 24 06:05:19 2017
2017-04-24 06:05:19,819 process L0479 DEBUG| [stderr] mdadm: Note: this array has metadata at the start and
2017-04-24 06:05:19,819 process L0479 DEBUG| [stderr] may not be suitable as a boot device. If you plan to
2017-04-24 06:05:19,820 process L0479 DEBUG| [stderr] store '/boot' on this device please ensure that
2017-04-24 06:05:19,820 process L0479 DEBUG| [stderr] your boot-loader understands md/v1.x metadata, or use
2017-04-24 06:05:19,820 process L0479 DEBUG| [stderr] --metadata=0.90
2017-04-24 06:05:19,820 process L0479 DEBUG| [stderr] mdadm: super1.x cannot open /dev/dm-6: Device or resource busy
2017-04-24 06:05:19,820 process L0479 DEBUG| [stderr] mdadm: /dev/dm-6 is not suitable for this array.
2017-04-24 06:05:19,820 process L0479 DEBUG| [stderr] mdadm: create aborted
@naveedus Please verify if the PR (#487) solves the issue.
from avocado-misc-tests.
naveedus
commented on September 16, 2024
I verified the issue and now the created raid array is stopped and exits cleanly.
we can close this issue.
meantime I found that minimum 3 disks are required to test RAID1, where 3rd disk is used as spare device used for fail-over.
Interestingly now with 3 disks the test runs RAID 5 test as well which I feel is wrong.
How can mdadm create RAID5 with two disks?
======console logs snippet====
2017-05-18 06:22:50,686 process L0499 INFO | Command 'echo 'yes' | mdadm --create --verbose --assume-clean /dev/md/mdsraid --level=5 --raid-devices=2 /dev/dm-10 /dev/dm-9 --spare-devices=1 /dev/dm-8 --force' finished with 0 after 0.0735051631927s
2017-05-18 06:22:50,686 process L0389 INFO | Running 'mdadm --detail /dev/md/mdsraid'
2017-05-18 06:22:50,694 process L0479 DEBUG| [stdout] /dev/md/mdsraid:
2017-05-18 06:22:50,694 process L0499 INFO | Command 'mdadm --detail /dev/md/mdsraid' finished with 0 after 0.0042929649353s
2017-05-18 06:22:50,694 process L0479 DEBUG| [stdout] Version : 1.2
2017-05-18 06:22:50,694 process L0479 DEBUG| [stdout] Creation Time : Thu May 18 06:22:50 2017
2017-05-18 06:22:50,694 process L0479 DEBUG| [stdout] Raid Level : raid5
2017-05-18 06:22:50,695 process L0479 DEBUG| [stdout] Array Size : 378732544 (361.19 GiB 387.82 GB)
2017-05-18 06:22:50,695 process L0479 DEBUG| [stdout] Used Dev Size : 378732544 (361.19 GiB 387.82 GB)
2017-05-18 06:22:50,695 process L0479 DEBUG| [stdout] Raid Devices : 2
2017-05-18 06:22:50,695 process L0479 DEBUG| [stdout] Total Devices : 3
2017-05-18 06:22:50,695 process L0479 DEBUG| [stdout] Persistence : Superblock is persistent
2017-05-18 06:22:50,695 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,695 process L0479 DEBUG| [stdout] Intent Bitmap : Internal
2017-05-18 06:22:50,696 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,696 process L0479 DEBUG| [stdout] Update Time : Thu May 18 06:22:50 2017
2017-05-18 06:22:50,696 process L0479 DEBUG| [stdout] State : clean
2017-05-18 06:22:50,696 process L0479 DEBUG| [stdout] Active Devices : 2
2017-05-18 06:22:50,696 process L0479 DEBUG| [stdout] Working Devices : 3
2017-05-18 06:22:50,696 process L0479 DEBUG| [stdout] Failed Devices : 0
2017-05-18 06:22:50,696 process L0479 DEBUG| [stdout] Spare Devices : 1
2017-05-18 06:22:50,697 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,697 process L0479 DEBUG| [stdout] Layout : left-symmetric
2017-05-18 06:22:50,697 process L0479 DEBUG| [stdout] Chunk Size : 512K
2017-05-18 06:22:50,697 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,697 process L0479 DEBUG| [stdout] Consistency Policy : bitmap
2017-05-18 06:22:50,697 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,697 process L0479 DEBUG| [stdout] Name : linux-0a5l:mdsraid (local to host linux-0a5l)
2017-05-18 06:22:50,698 process L0479 DEBUG| [stdout] UUID : e0214914:eeb25c1d:8d7644de:af154f3a
2017-05-18 06:22:50,698 process L0479 DEBUG| [stdout] Events : 0
2017-05-18 06:22:50,698 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,698 process L0479 DEBUG| [stdout] Number Major Minor RaidDevice State
2017-05-18 06:22:50,698 process L0479 DEBUG| [stdout] 0 254 10 0 active sync /dev/dm-10
2017-05-18 06:22:50,698 process L0479 DEBUG| [stdout] 1 254 9 1 active sync /dev/dm-9
2017-05-18 06:22:50,698 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,699 process L0479 DEBUG| [stdout] 2 254 8 - spare /dev/dm-8
2017-05-18 06:22:50,699 process L0389 INFO | Running 'mdadm --fail /dev/md/mdsraid /dev/dm-9'
2017-05-18 06:22:50,702 process L0479 DEBUG| [stderr] mdadm: set /dev/dm-9 faulty in /dev/md/mdsraid
2017-05-18 06:22:50,702 process L0499 INFO | Command 'mdadm --fail /dev/md/mdsraid /dev/dm-9' finished with 0 after 0.00182104110718s
2017-05-18 06:22:50,703 process L0389 INFO | Running 'mdadm --detail /dev/md/mdsraid'
2017-05-18 06:22:50,708 process L0479 DEBUG| [stdout] /dev/md/mdsraid:
2017-05-18 06:22:50,708 process L0499 INFO | Command 'mdadm --detail /dev/md/mdsraid' finished with 0 after 0.00380706787109s
2017-05-18 06:22:50,709 process L0479 DEBUG| [stdout] Version : 1.2
2017-05-18 06:22:50,709 process L0479 DEBUG| [stdout] Creation Time : Thu May 18 06:22:50 2017
2017-05-18 06:22:50,709 process L0479 DEBUG| [stdout] Raid Level : raid5
2017-05-18 06:22:50,709 process L0479 DEBUG| [stdout] Array Size : 378732544 (361.19 GiB 387.82 GB)
2017-05-18 06:22:50,709 process L0479 DEBUG| [stdout] Used Dev Size : 378732544 (361.19 GiB 387.82 GB)
2017-05-18 06:22:50,709 process L0479 DEBUG| [stdout] Raid Devices : 2
2017-05-18 06:22:50,710 process L0479 DEBUG| [stdout] Total Devices : 3
2017-05-18 06:22:50,710 process L0479 DEBUG| [stdout] Persistence : Superblock is persistent
2017-05-18 06:22:50,710 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,710 process L0479 DEBUG| [stdout] Intent Bitmap : Internal
2017-05-18 06:22:50,710 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,710 process L0479 DEBUG| [stdout] Update Time : Thu May 18 06:22:50 2017
2017-05-18 06:22:50,711 process L0479 DEBUG| [stdout] State : clean, degraded
2017-05-18 06:22:50,711 process L0479 DEBUG| [stdout] Active Devices : 1
2017-05-18 06:22:50,711 process L0479 DEBUG| [stdout] Working Devices : 2
2017-05-18 06:22:50,711 process L0479 DEBUG| [stdout] Failed Devices : 1
2017-05-18 06:22:50,711 process L0479 DEBUG| [stdout] Spare Devices : 1
2017-05-18 06:22:50,711 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,711 process L0479 DEBUG| [stdout] Layout : left-symmetric
2017-05-18 06:22:50,712 process L0479 DEBUG| [stdout] Chunk Size : 512K
2017-05-18 06:22:50,712 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,712 process L0479 DEBUG| [stdout] Consistency Policy : bitmap
2017-05-18 06:22:50,712 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,712 process L0479 DEBUG| [stdout] Name : linux-0a5l:mdsraid (local to host linux-0a5l)
2017-05-18 06:22:50,712 process L0479 DEBUG| [stdout] UUID : e0214914:eeb25c1d:8d7644de:af154f3a
2017-05-18 06:22:50,712 process L0479 DEBUG| [stdout] Events : 1
2017-05-18 06:22:50,713 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,713 process L0479 DEBUG| [stdout] Number Major Minor RaidDevice State
2017-05-18 06:22:50,713 process L0479 DEBUG| [stdout] 0 254 10 0 active sync /dev/dm-10
2017-05-18 06:22:50,713 process L0479 DEBUG| [stdout] 1 254 9 1 faulty /dev/dm-9
2017-05-18 06:22:50,713 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,713 process L0479 DEBUG| [stdout] 2 254 8 - spare /dev/dm-8
2017-05-18 06:22:50,714 process L0389 INFO | Running 'mdadm --manage /dev/md/mdsraid --remove /dev/dm-9'
2017-05-18 06:22:50,810 process L0479 DEBUG| [stderr] mdadm: hot removed /dev/dm-9 from /dev/md/mdsraid
2017-05-18 06:22:50,810 process L0499 INFO | Command 'mdadm --manage /dev/md/mdsraid --remove /dev/dm-9' finished with 0 after 0.0948021411896s
2017-05-18 06:22:50,811 process L0389 INFO | Running 'mdadm --detail /dev/md/mdsraid'
2017-05-18 06:22:50,829 process L0479 DEBUG| [stdout] /dev/md/mdsraid:
2017-05-18 06:22:50,829 process L0499 INFO | Command 'mdadm --detail /dev/md/mdsraid' finished with 0 after 0.016893863678s
2017-05-18 06:22:50,830 process L0479 DEBUG| [stdout] Version : 1.2
2017-05-18 06:22:50,830 process L0479 DEBUG| [stdout] Creation Time : Thu May 18 06:22:50 2017
2017-05-18 06:22:50,831 process L0479 DEBUG| [stdout] Raid Level : raid5
2017-05-18 06:22:50,831 process L0479 DEBUG| [stdout] Array Size : 378732544 (361.19 GiB 387.82 GB)
2017-05-18 06:22:50,831 process L0479 DEBUG| [stdout] Used Dev Size : 378732544 (361.19 GiB 387.82 GB)
2017-05-18 06:22:50,831 process L0479 DEBUG| [stdout] Raid Devices : 2
2017-05-18 06:22:50,831 process L0479 DEBUG| [stdout] Total Devices : 2
2017-05-18 06:22:50,832 process L0479 DEBUG| [stdout] Persistence : Superblock is persistent
2017-05-18 06:22:50,832 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,832 process L0479 DEBUG| [stdout] Intent Bitmap : Internal
2017-05-18 06:22:50,832 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,832 process L0479 DEBUG| [stdout] Update Time : Thu May 18 06:22:50 2017
2017-05-18 06:22:50,832 process L0479 DEBUG| [stdout] State : clean, degraded, recovering
2017-05-18 06:22:50,833 process L0479 DEBUG| [stdout] Active Devices : 1
2017-05-18 06:22:50,833 process L0479 DEBUG| [stdout] Working Devices : 2
2017-05-18 06:22:50,833 process L0479 DEBUG| [stdout] Failed Devices : 0
2017-05-18 06:22:50,833 process L0479 DEBUG| [stdout] Spare Devices : 1
2017-05-18 06:22:50,833 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,833 process L0479 DEBUG| [stdout] Layout : left-symmetric
2017-05-18 06:22:50,834 process L0479 DEBUG| [stdout] Chunk Size : 512K
2017-05-18 06:22:50,834 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,834 process L0479 DEBUG| [stdout] Consistency Policy : bitmap
2017-05-18 06:22:50,834 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,834 process L0479 DEBUG| [stdout] Rebuild Status : 0% complete
2017-05-18 06:22:50,834 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,835 process L0479 DEBUG| [stdout] Name : linux-0a5l:mdsraid (local to host linux-0a5l)
2017-05-18 06:22:50,835 process L0479 DEBUG| [stdout] UUID : e0214914:eeb25c1d:8d7644de:af154f3a
2017-05-18 06:22:50,835 process L0479 DEBUG| [stdout] Events : 2
2017-05-18 06:22:50,835 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,835 process L0479 DEBUG| [stdout] Number Major Minor RaidDevice State
2017-05-18 06:22:50,835 process L0479 DEBUG| [stdout] 0 254 10 0 active sync /dev/dm-10
2017-05-18 06:22:50,836 process L0479 DEBUG| [stdout] 2 254 8 1 spare rebuilding /dev/dm-8
2017-05-18 06:22:50,836 process L0389 INFO | Running 'mdadm --manage /dev/md/mdsraid --add /dev/dm-9'
2017-05-18 06:22:50,876 process L0499 INFO | Command 'mdadm --manage /dev/md/mdsraid --add /dev/dm-9' finished with 0 after 0.037789106369s
2017-05-18 06:22:50,876 process L0479 DEBUG| [stderr] mdadm: re-added /dev/dm-9
2017-05-18 06:22:50,877 process L0389 INFO | Running 'mdadm --detail /dev/md/mdsraid'
2017-05-18 06:22:50,994 process L0479 DEBUG| [stdout] /dev/md/mdsraid:
2017-05-18 06:22:50,994 process L0499 INFO | Command 'mdadm --detail /dev/md/mdsraid' finished with 0 after 0.115511894226s
2017-05-18 06:22:50,995 process L0479 DEBUG| [stdout] Version : 1.2
2017-05-18 06:22:50,995 process L0479 DEBUG| [stdout] Creation Time : Thu May 18 06:22:50 2017
2017-05-18 06:22:50,995 process L0479 DEBUG| [stdout] Raid Level : raid5
2017-05-18 06:22:50,995 process L0479 DEBUG| [stdout] Array Size : 378732544 (361.19 GiB 387.82 GB)
2017-05-18 06:22:50,996 process L0479 DEBUG| [stdout] Used Dev Size : 378732544 (361.19 GiB 387.82 GB)
2017-05-18 06:22:50,996 process L0479 DEBUG| [stdout] Raid Devices : 2
2017-05-18 06:22:50,996 process L0479 DEBUG| [stdout] Total Devices : 3
2017-05-18 06:22:50,996 process L0479 DEBUG| [stdout] Persistence : Superblock is persistent
2017-05-18 06:22:50,996 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,996 process L0479 DEBUG| [stdout] Intent Bitmap : Internal
2017-05-18 06:22:50,997 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,997 process L0479 DEBUG| [stdout] Update Time : Thu May 18 06:22:50 2017
2017-05-18 06:22:50,997 process L0479 DEBUG| [stdout] State : clean, degraded, recovering
2017-05-18 06:22:50,997 process L0479 DEBUG| [stdout] Active Devices : 1
2017-05-18 06:22:50,997 process L0479 DEBUG| [stdout] Working Devices : 3
2017-05-18 06:22:50,998 process L0479 DEBUG| [stdout] Failed Devices : 0
2017-05-18 06:22:50,998 process L0479 DEBUG| [stdout] Spare Devices : 2
2017-05-18 06:22:50,998 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,998 process L0479 DEBUG| [stdout] Layout : left-symmetric
2017-05-18 06:22:50,998 process L0479 DEBUG| [stdout] Chunk Size : 512K
2017-05-18 06:22:50,998 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,999 process L0479 DEBUG| [stdout] Consistency Policy : bitmap
2017-05-18 06:22:50,999 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,999 process L0479 DEBUG| [stdout] Rebuild Status : 0% complete
2017-05-18 06:22:50,999 process L0479 DEBUG| [stdout]
2017-05-18 06:22:50,999 process L0479 DEBUG| [stdout] Name : linux-0a5l:mdsraid (local to host linux-0a5l)
2017-05-18 06:22:50,999 process L0479 DEBUG| [stdout] UUID : e0214914:eeb25c1d:8d7644de:af154f3a
2017-05-18 06:22:51,000 process L0479 DEBUG| [stdout] Events : 5
2017-05-18 06:22:51,000 process L0479 DEBUG| [stdout]
2017-05-18 06:22:51,000 process L0479 DEBUG| [stdout] Number Major Minor RaidDevice State
2017-05-18 06:22:51,001 process L0479 DEBUG| [stdout] 0 254 10 0 active sync /dev/dm-10
2017-05-18 06:22:51,001 process L0479 DEBUG| [stdout] 2 254 8 1 spare rebuilding /dev/dm-8
2017-05-18 06:22:51,001 process L0479 DEBUG| [stdout]
2017-05-18 06:22:51,001 process L0479 DEBUG| [stdout] 1 254 9 - spare /dev/dm-9
2017-05-18 06:22:51,002 process L0389 INFO | Running 'mdadm --manage /dev/md/mdsraid --stop'
2017-05-18 06:22:51,230 process L0479 DEBUG| [stderr] mdadm: stopped /dev/md/mdsraid
2017-05-18 06:22:51,230 process L0499 INFO | Command 'mdadm --manage /dev/md/mdsraid --stop' finished with 0 after 0.22633600235s
2017-05-18 06:22:51,231 process L0389 INFO | Running 'mdadm --assemble /dev/md/mdsraid /dev/dm-10 /dev/dm-9 /dev/dm-8'
2017-05-18 06:22:51,320 process L0479 DEBUG| [stderr] mdadm: /dev/md/mdsraid has been started with 1 drive (out of 2), 1 rebuilding and 1 spare.
2017-05-18 06:22:51,384 process L0499 INFO | Command 'mdadm --assemble /dev/md/mdsraid /dev/dm-10 /dev/dm-9 /dev/dm-8' finished with 0 after 0.151476860046s
2017-05-18 06:22:51,384 process L0389 INFO | Running 'mdadm --detail /dev/md/mdsraid | grep State | grep recovering'
2017-05-18 06:22:51,475 process L0479 DEBUG| [stdout] State : clean, degraded, recovering
from avocado-misc-tests.
Related Issues (20)
- After running dapl.py in Rhel8.4 with Avocado (version: 90.0), it shows “Cancel: failed connecting to peer”. HOT 1
- When using ib_pingpong.py of Avocado (version: 90.0) to test MLNX Network-Card in Rhel8.4, it shows “FAIL: test failed”. HOT 1
- When using rdma_tests.py of Avocado (version: 90.0) to test MLNX Network-Card in Rhel8.4, it shows “FAIL: Client cmd: ib_atomic_bw -F”. HOT 1
- After running perf_fuzzer.py in Rhel8.4 with Avocado (version: 93.0), it shows “RuntimeError: Test interrupted by SIGTERM”. HOT 3
- While running ndctl.py with Avocado 92.0, traceback messages are seen [(most recent call last):File "/usr/lib64/python3.6/multiprocessing/process.py"..] HOT 1
- After running avago9361_vd.py in Rhel8.4 with Avocado (version: 93.0), it shows “FAIL: Failed to set drive to online state”. HOT 1
- After running xfstests.py in Rhel8.4 OS with Avocado (version: 93.0), Rhel8.4 OS will automatically reboot and can't complete the test of xfstests.py. HOT 3
- When using disk_info.py to test NVMe-SSD in Rhel8.2 with Avocado (version: 94.0), it shows "\nGiven disk nvme11n1 is not present in lshw -c disk | grep -i nvme11n1\nGiven disk nvme11n1 not having uuid". HOT 1
- When using module_unload_load.py to test NVMe-SSD in Rhel8.3 with Avocado (version: 94.0), it shows "FAIL: Failed Modules: ['nvme']". HOT 1
- When using nvme_cli_selftests.py to test NVMe-SSD in Rhel8.3 with Avocado (version: 94.0), nvme_compare_test and nvme_smart_log_test are FAIL, but Manual-Test are PASS. HOT 1
- When using nvmetest.py to test NVMe-SSD in Rhel8.3 with Avocado (version: 94.0), it shows "ERROR: Command 'make' failed" and "CANCEL: /dev/nvme11n1 does not exist". HOT 1
- bonding.py : bonding tests fails for active-backup tests HOT 1
- multipath_test.py: Need proper clean up of paths after each tests run HOT 1
- After running nvme_cli_selftests.py in Rhel8.4, “run-test-nvme_compare_test-1521” & “run-test-nvme_get_features_test-0994” are FAIL HOT 1
- After running nvmetest.py in Rhel8.4, it shows “No such file or directory: './NVME-VERSION-GEN'” HOT 1
- pread fail case in random test code while running in multiple threads HOT 7
- perf_uprobe error handling HOT 1
- Stress-ng Failing HOT 5
- fio-pmem test failing HOT 2
- Run failed: xfstests - iommu (cba565f) HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from avocado-misc-tests.