running it locally to see if I can reproduce, but I can repro it consistently across all three build agents
on different PRs
:facepunch:
running packet.exe install manually fails trying to get SourceLink.Fake now
is what I get
this is probably punishment for being away this long :D
@stefansedich restored just fine for me - rebuilding it again without any packages
will try again at home
just in case
ok weird, getting a pass now for #1430
despite having two failures on the F# DU serialization test with Wire cc @rogeralsing
what could cause an intermittent failure with that spec?
@stefansedich doing a full rebuild from a clean clone of the dev branch of the main Akka.NET repo
basically what our build server does
must be your network
will try tonight
lol wtf, running packet install on a fresh clone
comes up with some garbled text then my speakers start playing a ding sound
constantly
no idea where this bug is
with Azure or the TC plugin
looked to me like Azure was reporting the wrong hostname
but if you sysprep the VM and use that image
the name of that VM gets burned into the new VM using that image initially
so all of the auto-scaled build servers report themselves as the same instance name
however, if you just save the VM without sysprep
then the correct name gets assigned from the start
ridiculous and weird
but there you have it
btw, with the sysprepped VMs
their name DOES change after its booted
in the azure metadata
where the agent reads its name from
so if you RDP into each agent and restart the TC Agent service it will work