Closed tarekgh closed 3 months ago
CC @stephentoub @ericstj @luisquintanilla @michaelgsharp @LittleLittleCloud
Attention: Patch coverage is 69.70443%
with 369 lines
in your changes are missing coverage. Please review.
Project coverage is 68.48%. Comparing base (
8b483f4
) to head (130583b
). Report is 2 commits behind head on main.
@agocke any idea why build analysis is failing while all reported issues are known issues? I can force merge without waiting but I want to know if there is anything wrong here.
CC @ericstj
Seems like it should be passing to me. @AlitzelMendez any ideas?
I think this is due to a problem with how machinelearning reports helix failures. https://github.com/dotnet/machinelearning/issues/7044
I noticed it but haven't gotten around to fixing it yet.
Edit: Maybe not since if that were the case I would have expected at least one thing showing up as not "known". Here everything is known. Seems like an issue with Build Analysis
Ok, I'll go ahead and force merge.
Maybe not since if that were the case I would have expected at least one thing showing up as not "known". Here everything is known. Seems like an issue with Build Analysis
I am noticing the build analysis is pointing at one leg only that failed and known. But looks nothing mentioned the rest of failed legs.
I think I realize what's going on here. Just connected this to another issue we were talking about in chat. This build has many legs that were cancelled. I suspect that's why Build Analysis is staying red (it would be nice if that were made clear in UI). If legs are cancelled it means tests may not have even run, so it's not safe to treat the PR as passing. It looks to me like many of the build legs for this timed-out while waiting for helix to run the work-items. For some it looks like they eventually completed, for others they are still "waiting".
Seems like it should be passing to me. @AlitzelMendez any ideas?
Hi Andy, this is an opt-in feature which is not activated for this repository, do we want to add this repository?
@AlitzelMendez my team owns this repo - can you clarify what you mean by opt-in feature? What feature is opt-in?
This change is introducing the Llama tokenizer which is implemented as the SentencePiece Bpe model based on https://github.com/google/sentencepiece.