[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Are we ready to block on autopkgtest regressions?

Dear release team,

Three days ago I opened a merge request against brintey2 [1] to enable
britney2 to block migrations that cause regressions in autopkgtest
results in testing. Niels copied it to the IRC channel, but we saw no
reactions so far from other RT members. We were wondering what the
opinions in the team are: should we go for it? And if not, what are the
issues that you consider to be in need of fixing first.

The infrastructure isn't perfect yet (let that not be the enemy of
good); it is our intent to keep on fixing issues. IMHO the system is
behaving sane enough that only some pushes here and there are needed, so
I'd say: let's go for it.

P.S. I already prepared an announcement on gobby [2]. Improvements to or
comments on that message are welcome as well.
P.S.2 Steve McIntyre hinted [3] that arm64 servers will become available
for autopkgtesting on a reasonable time scale.

[1] https://salsa.debian.org/release-team/britney2/merge_requests/9
[2] https://gobby.debian.org/export/Teams/Release/autopkgtest%20gating
[3] https://lists.debian.org/debian-devel/2018/09/msg00203.html

Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: