Charles Oliveira

Thanks for the change @roxell ! I've incorporated that here https://github.com/Linaro/squad/commit/76892b8510d9e2f131a13becd4a52a6db081ceac

@laurent-alfonsi-linaro Could you please try using `someannotation`? I tried it locally and it worked.

I'll review your patch today, as celery tagging was done by this commit: https://github.com/Linaro/squad/commit/47fd9f90fa6ae64d4563c4eb941b6ab2bce1488d

Bummer! Changing celery to that also changed django-celery-results, which is used when fetching android test jobs (+2M tests) and got this error while fetching ``` File "/home/chaws/.local/lib/python3.10/site-packages/django_celery_results/backends/database.py", line 123, in...

This has been fixed in django-celery-results: https://github.com/celery/django-celery-results/commit/d5c4456e018ccd2b219aa5ff607424dbae7b926f

Updating django-celery-results require a database migration ``` django.db.utils.ProgrammingError: column django_celery_results_taskresult.periodic_task_name does not exist LINE 1: ...d", "django_celery_results_taskresult"."task_id", "django_ce... ``` I'll put this PR in the back burner as higher priority...

For future references: I used two builds in staging [baseline](https://staging-qa-reports.linaro.org/~charles.oliveira/test-android-cts-parallel-processing/build/last-build-with-1M-tests/) and [target](https://staging-qa-reports.linaro.org/~charles.oliveira/test-android-cts-parallel-processing/build/one-last-attempt/) to use as PoC that using build reference in Test table would make things significantly faster. Those builds...

I slept on it and I also think having the environment reference to test table is fundamental to make correct comparisons. There are cases where the same test is run...

sorry for delay! If I change this to be an url, instead of an id, how much of your stuff will it break?

Closing it due to the same reason of https://github.com/Linaro/squad/issues/180. I think the list can be written in the email template. Please re-open if I'm wrong