Home → Problems →

Build process abortion?

• Edit

Kosta

22 Jan, 2015 10:56 PM

Hey AppVeyors,

Why is the build process constantly aborting for this project (https://ci.appveyor.com/project/Kosta-Github/cppcheck) when starting to compile the first source file? It looks like this is only happening for the debug configs. Note that this is not a compilation issue of the project, the compilation is just aborted after a longer period of time without any diagnose message.

BTW, the project needs about less than one minute to build and run all tests on my local machine. Within the AppVeyor machine it takes 10-20 times longer. So might this be an issue with an under-resourced VM image running out of memory or so?

1. Support Staff 1 Posted by Feodor Fitsner on 23 Jan, 2015 12:57 AM

   

   I'm wondering why this one worked: https://ci.appveyor.com/project/Kosta-Github/cppcheck/build/1.69.5

   • Edit

2. 2 Posted by Kosta on 23 Jan, 2015 07:49 AM

   

   Yeah, but what about all the others? There hasn't been any change to the code in between... I just changed the `verbosity` setting from `minimal` to `detailed` (which passed the build as you mentioned above) and then back to `minimal` ...

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 23 Jan, 2015 06:33 PM

   

   So it works with "detailed" and doesn't with "minimal"?

   -Feodor

   • Edit

4. 4 Posted by Kosta on 23 Jan, 2015 08:41 PM

   

   Ok, tried some more builds with different settings for 'verbosity':
   - minimal: failing
   - normal: failing
   - detailed: triggered and in the queue, still waiting for the results
   But happens only for the debug configs but for both archs (win32 and x64)...

   • Edit

5. 5 Posted by Kosta on 24 Jan, 2015 10:10 AM

   

   Also 'detailed' is failing. But all the debug builds are working locally.

   Must be something within your VMs. How can that be debugged or tracked down? Maybe something related to your custom reporters?

   • Edit

6. Support Staff 6 Posted by Feodor Fitsner on 24 Jan, 2015 10:11 PM

   

   OK, it worked without AV msbuild logger: https://ci.appveyor.com/project/Kosta-Github/cppcheck/build/1.69.12

   • Edit

7. 7 Posted by Kosta on 26 Jan, 2015 05:45 PM

   

   Thx for that; so it is an issue with the AV logger than? What does the logger actually do?

   For this project the first file (tinyxml2.cpp) that gets compiled issues some compiler warnings (in debug mode only), which looks like dead-locking the AV logger then. Later compiler warnings seem to work fine so...

   • Edit

8. Support Staff 8 Posted by Feodor Fitsner on 26 Jan, 2015 05:51 PM

   

   Hm, that's good to know. I'll take a look what's going on there.

   • Edit

9. Support Staff 9 Posted by Feodor Fitsner on 26 Jan, 2015 06:59 PM

   

   I ran few builds for Win32/Debug trying to reproduce the issue: https://ci.appveyor.com/project/FeodorFitsner/cppcheck/history

   Seems like it is not reproducible on "Pro" environment (Hyper-V).

   • Edit

10. 10 Posted by Kosta on 29 Jan, 2015 05:59 AM

    

    so what is the conclusion from that?

    • Edit

11. Support Staff 11 Posted by Feodor Fitsner on 29 Jan, 2015 06:00 AM

    

    Don't know yet - need more testing.

    Do not use AppVeyor msbuild logger for now.

    • Edit

12. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:53 AM.