-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
avocado 102+ has removed some log messages which are useful for our debugging #5721
Comments
Hi @dzhengfy, thank you for your detailed description. I can confirm that these two are bugs and we will fix them for 103LTS version. We would like to keep the format from 92LTS as much as possible.
Unfortunately, this is needed for parallel run of multiple tests to keep track of which log is part of which test. I understand that this doesn't make sense for one test, but we don't want to bring more complexity to the logging system to differentiate single and multiple tests.
We have an open issue #5469 about this topic and we plan to work on it, but unfortunately right now we are working on fixing bugs and stabilization before LTS version. Therefore, we don't plan to have it in the near future. |
This commit addresses compatibility concerns by reverting the log message format of Avocado instrumented tests back to the 92LTS (Long-Term Support) version. By doing so, we ensure compatibility with the upcoming LTS version. Reference: avocado-framework#5721 Signed-off-by: Jan Richter <jarichte@redhat.com>
This commit addresses compatibility concerns by reverting the log message format of Avocado instrumented tests back to the 92LTS (Long-Term Support) version. By doing so, we ensure compatibility with the upcoming LTS version. Reference: avocado-framework#5721 Signed-off-by: Jan Richter <jarichte@redhat.com>
This commit addresses compatibility concerns by reverting the log message format of Avocado instrumented tests back to the 92LTS (Long-Term Support) version. By doing so, we ensure compatibility with the upcoming LTS version. Reference: avocado-framework#5721 Signed-off-by: Jan Richter <jarichte@redhat.com>
Resolved by #5732 |
Hi avocado maintainers,
I ran one case by avocado command:
avocado run --vt-type libvirt memory_snapshot.delete.paused.type_qcow2
. Then I compare the log results from different avocado branches. See below:Summary:
Questions:
For above summarized items, is it possible to support by a configuration or else? If possible, that will be very convenient for our debugging work like before.
Details as below:
92lts + nrunner + job.log:
Good things are like:
master + runner+ debug.log:
Changes:
master + runner + full.log:
Additional changes:
The text was updated successfully, but these errors were encountered: