sorawee
2022-5-13 21:06:13

I think we need to do something like https://github.com/vmware-tanzu/community-edition/actions/runs/2253393437/workflow#L64 to avoid the current error


samth
2022-5-13 21:10:13

Did something change that led to that problem? I’m tempted to just turn that off.


sorawee
2022-5-13 21:13:51

https://github.com/racket/racket/commit/7c2ebef056e330af71f538043d95763ef9d4f2fe is the commit that changes from success to fail. But it doesn’t look like it’s actually relevant.


sorawee
2022-5-13 21:15:42

Oh, actually previously there’s also a problem, but they were warnings


sorawee
2022-5-13 21:16:00

Here’s from the previous commit, before the one I mentioned above



sorawee
2022-5-13 21:16:16

> Warning: An error occurred checking the status of the delivery. Error: Code Scanning could not process the submitted SARIF file: > rejecting SARIF, as there are more runs than allowed (33 > 15) It should still be processed in the background, but errors that occur during processing may not be reported. > Analysis upload status is failed.


sorawee
2022-5-13 21:16:56

Now it becomes:

> Error: Code Scanning could not process the submitted SARIF file: > rejecting SARIF, as there are more runs than allowed (33 > 15)


samth
2022-5-14 02:08:34

I wonder when those warning started