merge_tops : throw better error if top is invalid#15
Conversation
|
Full json dump of the top file won't be very readable... maybe limit it somehow (first X chars?). Ideally it should point at the file and line, but that's rather hard to do at this abstraction level... |
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025061003-4.3&flavor=pull-requests Test run included the following:
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025061004-4.3&flavor=update
Failed tests37 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/142375#dependencies 10 fixed
Unstable testsDetailsPerformance TestsPerformance degradation:10 performance degradations
Remaining performance tests:62 tests
|
|
@marmarek Thanks a lot! Yes, I agree. I am working on adding some nested loops in |
|
@marmarek Thanks a lot! Yes, I agree. I am working on adding some nested loops in Here's the WIP gist of what I was thinking. I switched from throwing an error to logging a warning because I thought that made the output a lot cleaner, but unfortunately that caused an error to come from the minion: I'm guessing the Sorry I haven't had time to fully understand how the whole system works. I don't believe it is documented anywhere? |
|
Actually, I'm thinking instead of looping over all the tops to check them before passing to |
This is a step towards fixing #9950. It doesn't show the file name that caused the error, so I'll look into adding a check higher level, too.