mirror of
https://github.com/odoo/runbot.git
synced 2025-03-17 16:35:47 +07:00
56e242a660
The initial idea to link an error to another one was a quick solution to group them if they where related, but this became challenging to copute metada regarding errors. - The displayed error message was not always consistent with the real root cause/the error that lead here. - The aggregates (lets says, linked buils ids) could be the one of the error, or from all error messages. Same for the versions, first seen, .. This is confusing to knwo what is the leist we are managing and what is the expecte result to display Main motivation: on a standard error page (will be changed to "assignment"), we want to have the list of error message that is related to this one. We want to know for each message (a real build error) what is the version, first seen, ... This will give more flexibility on the display, The assigned person/team/test-tags, ... are moved to this model The appearance data remains on the build error but are aggregate on the assignation. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| common.py | ||
| test_branch.py | ||
| test_build_config_step.py | ||
| test_build_error.py | ||
| test_build_stat.py | ||
| test_build.py | ||
| test_command.py | ||
| test_commit.py | ||
| test_cron.py | ||
| test_dockerfile.py | ||
| test_event.py | ||
| test_host.py | ||
| test_repo.py | ||
| test_runbot.py | ||
| test_schedule.py | ||
| test_upgrade.py | ||
| test_version.py | ||