avocado-vt
avocado-vt copied to clipboard
[WIP] migration: Support multiple hosts migration
Signed-off-by: Yongxue Hong [email protected]
This pull request introduces 8 alerts when merging b831c487951287250eba461661e90aadd3b6fea7 into 79229074a52966eb833f561cedfe193d75416fc9 - view on LGTM.com
new alerts:
- 3 for Unused local variable
- 2 for Variable defined multiple times
- 1 for Except block handles 'BaseException'
- 1 for Inconsistent equality and hashing
- 1 for Wrong number of arguments in a call
This pull request introduces 2 alerts when merging c6ebea7527755381826f28e892129ea7d2de6357 into 79229074a52966eb833f561cedfe193d75416fc9 - view on LGTM.com
new alerts:
- 1 for Wrong name for an argument in a call
- 1 for Except block handles 'BaseException'
This pull request introduces 1 alert when merging ae12ca9e29be318182a670d2c54dc190ed8d3f79 into 79229074a52966eb833f561cedfe193d75416fc9 - view on LGTM.com
new alerts:
- 1 for Except block handles 'BaseException'
This pull request introduces 2 alerts when merging 93400c25ef8b2045ba5497ab245f77c6917ffe47 into 5ae052e859b74671f4e1e93c4e58320789f62d7d - view on LGTM.com
new alerts:
- 1 for Except block handles 'BaseException'
- 1 for Should use a 'with' statement
This pull request introduces 2 alerts when merging ecdfa5eb3099a93bb35e1303148320ea98e08da8 into 5ae052e859b74671f4e1e93c4e58320789f62d7d - view on LGTM.com
new alerts:
- 1 for Except block handles 'BaseException'
- 1 for Should use a 'with' statement
This pull request introduces 2 alerts when merging 8da5b96038e004db95ac5b5616a0d9c26c136836 into 5ae052e859b74671f4e1e93c4e58320789f62d7d - view on LGTM.com
new alerts:
- 1 for Except block handles 'BaseException'
- 1 for Should use a 'with' statement
This pull request introduces 5 alerts when merging 5b289260cfc1f8bcc24d7eb9ebc26f453a649049 into e3440ed1d2a4ab8185fdb77ac89119ccc5bb9f9c - view on LGTM.com
new alerts:
- 2 for Unused import
- 1 for Except block handles 'BaseException'
- 1 for Should use a 'with' statement
- 1 for Module is imported with 'import' and 'import from'
This pull request introduces 5 alerts when merging fdee4f64f261230abd5a46ac64edd01550cd45a2 into 3dc994568bd684debcb47cc30dad1e83c4b0857b - view on LGTM.com
new alerts:
- 2 for Unused import
- 1 for Except block handles 'BaseException'
- 1 for Should use a 'with' statement
- 1 for Module is imported with 'import' and 'import from'
This pull request introduces 5 alerts when merging 7a449019f13780a9cd5d76069df5d4a2a23aa833 into 3dc994568bd684debcb47cc30dad1e83c4b0857b - view on LGTM.com
new alerts:
- 2 for Unused import
- 1 for Except block handles 'BaseException'
- 1 for Should use a 'with' statement
- 1 for Module is imported with 'import' and 'import from'
This pull request introduces 5 alerts when merging 8d30696aaa37b98c6c8e4aad5beb4c0676aedd6c into 0024af92ba5b1f68793a7ba273daf9a8ceb5af6b - view on LGTM.com
new alerts:
- 2 for Unused import
- 1 for Except block handles 'BaseException'
- 1 for Should use a 'with' statement
- 1 for Module is imported with 'import' and 'import from'
This pull request introduces 4 alerts when merging b4ffa7e78400c3289ae7d600b285016fb10363ca into c197cfcb334aebb578f7f483bfb04dbb6d50b0f7 - view on LGTM.com
new alerts:
- 2 for Unused import
- 1 for Except block handles 'BaseException'
- 1 for Module is imported with 'import' and 'import from'
This pull request introduces 5 alerts when merging 32c455c5bc3f660ca0a3105a5e939fdff24fd8ed into 6e92a55fd4ce018df49d5bbf77bf994377ada0fd - view on LGTM.com
new alerts:
- 2 for Unused import
- 1 for Except block handles 'BaseException'
- 1 for Should use a 'with' statement
- 1 for Module is imported with 'import' and 'import from'
This pull request introduces 5 alerts when merging 682af4f648d87e3c51593d0a474820375498e55c into cd917beef1e1609163021a76085e34e3adaa3805 - view on LGTM.com
new alerts:
- 2 for Unused import
- 1 for Except block handles 'BaseException'
- 1 for Should use a 'with' statement
- 1 for Module is imported with 'import' and 'import from'
Interesting! Is there a whitepaper or a blueprint about this where we can read more about the planned architecture changes and approach to this?
Interesting! Is there a whitepaper or a blueprint about this where we can read more about the planned architecture changes and approach to this?
Hi @pevogam For the blueprint, we are clearing up the data, but there are still some places we haven't a conclusion yet, however, we will handle it ASAP.
For the general architecture, I think you could refer to this draft PR.
By the way @YongxueHong, just in case you are interested we also have a remote spawner PR in https://github.com/avocado-framework/avocado/pull/5621 using which I have already managed to run VT tests remotely and distribute them among multiple host machines.
By the way @YongxueHong, just in case you are interested we also have a remote spawner PR in avocado-framework/avocado#5621 using which I have already managed to run VT tests remotely and distribute them among multiple host machines.
Hi @pevogam Thanks for your information.
The main benefit is that we don't need any additional effort on the Avocado VT side since Avocado has already put most of the functionality in place. The same solution also easily integrates with the existing architecture.