If you look here: http://resultsdb-stg.cloud.fedoraproject.org/results?testcase_name=upgradepath the last successful upgradepath task was executed on Jun 24. Since then, there are no results. Because we don't store crashed results in ResultsDB yet, it's hard to tell how many upgradepath tasks were executed and with what arguments. However, from a somewhat tedious look through buildbot waterfall view it seems that all upgradepath failures were executed with updates-testing-pending: https://taskotron-stg.fedoraproject.org/taskmaster/builders/all/builds/7957/steps/runtask/logs/stdio (which is correct, upgradepath doesn't support that tag at the moment)
I haven't found any upgradepath failures with updates-pending. That means two options: a) upgradepath (and other checks) are not being scheduled on updates-pending at all b) upgradepath fails to push results to resultsdb
Martin had a look at jobs.csv on taskotron-stg01 machine, grepped for updates-pending and found 0 results. That supports option a).
jobs.csv
taskotron-stg01
updates-pending
Tim, Martin, please have a look at the infrastructure and current configuration of the trigger and find out why updates-pending tasks are not scheduled at all. Thanks.
PS: It seems that jobs.csv records end on Jul 01, there are no subsequent records at all. That is also highly suspicious and may indicate another problem.
This ticket had assigned some Differential requests: D186
I have trigger running in stream mode elsewhere and it does appear as if upgradepath is being scheduled properly right now
Probably a config issue, will look into it
Can you give me at least one buildbot link with upgradepath running with updates-pending? If they run, they don't report to resultsdb for some reason.
! In #278#7, @kparal wrote: I have trigger running in stream mode elsewhere and it does appear as if upgradepath is being scheduled properly right now Can you give me at least one buildbot link with upgradepath running with updates-pending? If they run, they don't report to resultsdb for some reason.
! In #278#7, @kparal wrote: I have trigger running in stream mode elsewhere and it does appear as if upgradepath is being scheduled properly right now
Sorry, that was a mistake when I was typing. It does not appear as if upgradepath is being scheduled properly right now.
I might have found the cause of the problem, working on a fix...
Metadata Update from @kparal: - Issue tagged with: infrastructure
Login to comment on this ticket.