Around the time v4.10 branched, we were starting to hit some flakiness with CI. It turns out the samba_ad_dc_2 job was starting to hit resource limits and could end up using swap. Depending on when the swap kicked in, it could mean the difference between a CI pass and a CI fail. Often the problem would manifest itself as a dns_hub error starting up the vampire_2000_dc. We have now split up the autobuild jobs to avoid this problem, but it should be backported to 4.10 to improve CI reliability.
Created attachment 14838 [details] Fix backport for v4.10 CI link: https://gitlab.com/catalyst-samba/samba/pipelines/46644585
Actually, as we need to still support python2 on 4.10, I should probably add a separate py2 target for the new backup autobuild job, just so we don't degrade python2 support for the backup/restore. I'll update the patch.
Created attachment 14915 [details] Additional patch as suggested by Tim for -py2
G'Day Karolin, Please take both patches for the next available 4.10.x CI: https://gitlab.com/samba-team/devel/samba/pipelines/51162805
(In reply to Andrew Bartlett from comment #4) Pushed both patches to autobuild-v4-10-test.
(In reply to Karolin Seeger from comment #5) Pushed to v4-10-test. Closing out bug report. Thanks!