I would hazard a guess and say 'no' because to my best knowledge, autopkgtests 
run independent of the build tree. If you need something left in the source 
tree you either need it packaged, or perhaps run the tests requiring those 
artifacts in your debian/rules as part of the build process. (Though, outside 
of a few rare cases I've seen I am not sure how effective this would be in 
practice, though it would guarantee it is run against the build tree.)


Sent from my T-Mobile 5G Device



-------- Original message --------
From: Lorenzo <[email protected]>
Date: 11/24/25 18:57 (GMT-05:00)
To: [email protected]
Subject: using build artifacts with autopkgtest

Hello Mentors,

I want to add the upstream testsuite of a package that I maintain
(socklog) to autopkgtest. However, when I do so, the test fails
because it uses two tiny C build artifacts (~40KiB) that are build only
to be used in the testsuite and are not part of the deb package.

Is there a way to access the uncleaned build tree from autopkgtest?

If not, I thought to add the two artifacts to the socklog.deb package,
but is there an appropriate path for it?
maybe /usr/lib/socklog/test/ ?

Lorenzo

Reply via email to