seed-new-release does not copy forward neutral test results

[Brian Murray]

During the opening of Mantic vorlon noticed that there were no results for debspawn on armhf and that the first result appears on 2023-05-04 which is sometime after the opening and britney being initialized.

https://autopkgtest.ubuntu.com/packages/debspawn/mantic/armhf

The seed-new-release code should be examined to see if neutral results are copied forward and if not fixed. If it is fixed then we could copy the results forward for any packages which fall into this category. Additionally, we probably don't need to check and see if tests for the packages have run since the archive opening because this would just add an earlier entry to the result set.

[Brian Murray (brian-murray)]

seed-new-release has the following:

 94 # get passing result per package/arch from database
 95 db_con = sqlite3.connect(args.results_db)
 96 for (package, arch, run_id) in db_con.execute(
 97 "SELECT package, arch, MAX(run_id) "
 98 "FROM test, result "
 99 "WHERE test.id = result.test_id AND release = '%s' "
100 " AND (exitcode = 0 OR exitcode = 2 "
101 " OR triggers = 'migration-reference/0') "
102 "GROUP BY package, arch" % args.old_release):

and autopgktest-web/webcontrol/browse.cgi has:

 88 if code in (8,):
 89 return 'neutral'

So no, neutral results are not copied forward.

[Tim Andersson (andersson123)]

https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/446929

MP for seed-new-release

[Tim Andersson (andersson123)]

I don't think we need to make any changes to browse.cgi right?

[Brian Murray (brian-murray)]

It's fixed in git but an updated charm with this change has not been deployed in production so I am setting this to Fix Committed.