[Toybox] Horrible microsoft github tests spamming me.

[enh]

On Tue, Aug 4, 2020 at 10:59 AM Eric Molitor <emolitor at molitor.org> wrote:
>
> You can download the raw logs by using the "triple dot" menu to the right of the search logs field. This may or may not help avoid the issues with the javascript on that page.
>
> If you add Elliott as a collaborator you can configure the notification route to go to him instead of you. (You can also disable them completely if you don't want them at all.)

it looks like i am a "collaborator"[1], but it looks like i can't
see/change the notifications myself?

___
1. am i the only one who shudders at that word because it's only
really used in connection with Vichy France, and has no positive
connotations for me?

> - Eric
>
> On Tue, Aug 4, 2020 at 4:38 PM enh via Toybox <toybox at lists.landley.net> wrote:
>>
>> On Mon, Aug 3, 2020 at 11:41 PM Rob Landley <rob at landley.net> wrote:
>> >
>> > I got email about https://github.com/landley/toybox/runs/940149373 in which one
>> > of the cpio tests spuriously failed. I cannot cut and paste the failure because
>> > microsoft github's crammed so much javascript into the reporting page that
>> > doesn't work.
>> >
>> > The last time cpio.c changed was april, the last time tests/cpio.test changed
>> > was may, and the last time lib/* or any of the scripts/test plumbing changed was
>> > June.
>> >
>> > The test failed for non-obvious reasons which look like a shell race condition
>> > with | or something? The test is doing a dd to grab a specific byte offset out
>> > of the file. and the chunk it's looking at starts 8 bytes too early to get a
>> > match with what it expects. Is this a dd problem? Is the file longer with
>> > spurious crap inserted earlier in it? Did the container's | insert extra data?
>> > Who knows, I haven't a clue how to dig any of the build artifacts out of this
>> > mess, but I got email about it.
>>
>> yeah, this is where i've been for years with the "found by Android CI"
>> bugs. one thing i can say is that i'm _not_ seeing this on Android's
>> CI. (an obvious difference there is that we use toybox dd!)
>>
>> anyway, the first time i see a failure i just take a mental note to
>> prime myself for future occurrences and assume cosmic ray/failing
>> hardware/bad kernel unless i see it again.
>>
>> the nice thing about CI though is that it doesn't take long before
>> it's run the tests more often than all the humans put together.
>>
>> > I thought I was not going to get these emails, and am sad. And to add insult,
>> > the github email says it's from "Rob Landley", which is very much not the case.
>>
>> annoyingly, i _want_ to get them, but don't. (and don't know how to
>> sign up for them either :-( )
>>
>> > Rob
>> > _______________________________________________
>> > Toybox mailing list
>> > Toybox at lists.landley.net
>> > http://lists.landley.net/listinfo.cgi/toybox-landley.net
>> _______________________________________________
>> Toybox mailing list
>> Toybox at lists.landley.net
>> http://lists.landley.net/listinfo.cgi/toybox-landley.net