Thanks for using @Semmle QL for variant analysis. Since http://LGTM.com is free for OSS, we set a 4hr limit to ensure resources are avail to all teams. We are thinking of ways to get larger projects on http://LGTM.com . Let us know what you’d like to see analyzed
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I double-checked and I was surprised to see that Coverity didn't see this issue. As
@tehjh pointed out, sparse has been warning about it for a while since it's a argument type violation (but with a constructed type). I wonder if we could trick gcc or clang into seeing it too. -
2 things go to my "kernel dev process peculiarities" collection: - another case of lost patch - "sparse pointing to a bug" does not mean anything: not on anybody's radar, fix is still lost, not sparse warning that allowed to recover the fix
Kraj razgovora
Novi razgovor -
-
-
Amazing post, thank you !
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Just for clarification, LGTM Enterprise does not have a limit for build times. Typical customer deployments build much faster with infrastructure scaled to meet their needs.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.