[Github-comments] Re: [geany/geany] CodeQL CI failures (Issue #4206)

[Enrico Tröger via Github-comments]

Thanks for notifying.

I cleaned up #4208 and renamed it accordingly.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4206#issuecomment-2628520429
You are receiving this because you are subscribed to this thread.

Message ID: 

[Github-comments] Re: [geany/geany] CodeQL CI failures (Issue #4206)

[Jiří Techet via Github-comments]

The latest merges seem to be green again without any extra patch so it was 
probably a glitch on the github side.

Which doesn't mean that #4208 shouldn't be merged - no comments from me as I 
don't know anything about this stuff :-)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4206#issuecomment-2616388023
You are receiving this because you are subscribed to this thread.

Message ID: 

[Github-comments] Re: [geany/geany] CodeQL CI failures (Issue #4206)

[Enrico Tröger via Github-comments]

In #4208 I removed the "autobuild" step and replaced it with "build-mode: 
autobuild" as mentioned in the docs but it failed with a different error 
("could not compile"). So I reverted the changes again.

I also checked the version of the CodeQL action but the last successful build 
was using the same version as the failing builds.

Finally it got green after I replace "autobuild" with "manual" and added steps 
for running a simple Meson build.

While this is nice, I still have no clue why it doesn't work anymore with 
"autobuild" :(.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4206#issuecomment-2600876577
You are receiving this because you are subscribed to this thread.

Message ID: 

[Github-comments] Re: [geany/geany] CodeQL CI failures (Issue #4206)

[Enrico Tröger via Github-comments]

I also think caching is not involved here.

To be sure, I removed installing "ccache" in #4208, still I think it never had 
an effect as the cached artefacts from "ccache" were never persisted between 
workflow runs.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4206#issuecomment-2599702003
You are receiving this because you are subscribed to this thread.

Message ID: 

[Github-comments] Re: [geany/geany] CodeQL CI failures (Issue #4206)

[Jiří Techet via Github-comments]

> If you pushed to those branches multiple times, the subsequent builds used 
> cached objects; CodeQL was not built to cope with those:

Those failures now happen for every new PR.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4206#issuecomment-2594805340
You are receiving this because you are subscribed to this thread.

Message ID: 

[Github-comments] Re: [geany/geany] CodeQL CI failures (Issue #4206)

[rdipardo via Github-comments]

> I started getting it in [#4205](https://github.com/geany/geany/pull/4205) and 
> now it fails also for the merged 
> [#4095](https://github.com/geany/geany/pull/4095) in master.

If you pushed to those branches multiple times, the subsequent builds used 
cached objects; CodeQL was not built to cope with those: 

> Since CodeQL observes the activity of the compiler to understand the data 
> flows in a repository, CodeQL requires a complete build to take place in 
> order to perform analysis.
>
> 


-- 
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4206#issuecomment-2594581577
You are receiving this because you are subscribed to this thread.

Message ID: