From: helmut@subdivi.de 
  
 Hi Santiago, 
  
 On Tue, Sep 30, 2025 at 12:43:36AM +0200, Santiago Vila wrote: 
 > This is to announce that I plan to report bugs in this category 
 > ("FTBFS when using the nocheck build profile") on a regular basis for 
 > forky and beyond. 
  
 Thank you. I have been filing a number of these manually and am happy to 
 have that task automated. 
  
 > If you find a failure pattern different than those two having a 
 > significant number of occurrences, you are welcome to add it to the 
 > wiki page above. 
  
 Would you be able to occasionally do a more complex test? Occasionally, 
 the package actually cross builds with the nocheck build profile but 
 misses stuff. This is not technically a FTBFS, but it also violates the 
 definition of the nocheck build profile. 
  
 Here is a sketch of how to test this: 
  
    1. Perform a nocheck build 
       + failure? -> stop + report nocheck FTBFS 
    2. Perform a normal build 
       + failure? -> stop + report FTBFS 
    3. Compare the binary artifacts of these builds for equality 
       + equal? -> stop 
    4. Perform another normal build 
       + failure? -> stop + report random FTBFS 
    5. Compare the binary artifacts of the two normal builds 
       + equal? -> stop + report nocheck changing the result 
    6. Compare the content filenames of the nocheck build and the normal 
       build 
       + inequal? -> stop + report nocheck changing the result 
  
 What do you think? 
  
 Helmut 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)