Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 08:16
    AzureGulf commented #4360
  • 08:14
    AzureGulf commented #4360
  • 01:29
    Aaronontheweb commented #4360
  • 01:25
    Aaronontheweb synchronize #4361
  • 00:48
    Aaronontheweb synchronize #4361
  • 00:44
    Aaronontheweb opened #4361
  • Mar 27 20:32
    Aaronontheweb milestoned #4360
  • Mar 27 20:32
    Aaronontheweb commented #4360
  • Mar 27 20:32
    Aaronontheweb assigned #4360
  • Mar 27 20:32
    Aaronontheweb labeled #4360
  • Mar 27 20:32
    Aaronontheweb labeled #4360
  • Mar 27 19:18
    dependabot-preview[bot] synchronize #3986
  • Mar 27 19:18

    dependabot-preview[bot] on nuget

    Bump NUnit from 3.6.1 to 3.12.0… (compare)

  • Mar 27 19:18
    dependabot-preview[bot] edited #3986
  • Mar 27 19:18
    dependabot-preview[bot] synchronize #4337
  • Mar 27 19:18

    dependabot-preview[bot] on nuget

    Bump FSharp.Quotations.Evaluato… (compare)

  • Mar 27 19:18
    dependabot-preview[bot] edited #4337
  • Mar 27 19:17
    dependabot-preview[bot] edited #3986
  • Mar 27 19:17
    dependabot-preview[bot] edited #4337
  • Mar 27 19:16

    Aaronontheweb on dev

    Sharding update (#4354) * Avoi… (compare)

Tom Rathbone
@chillitom
System.MissingMethodException : Method not found: 'Void Nessos.FsPickler.BinarySerializer..ctor(Microsoft.FSharp.Core.FSharpOption1<Boolean>, Microsoft.FSharp.Core.FSharpOption1<Nessos.FsPickler.ITypeNameConverter>)'.
at Akka.FSharp.Serialization.ExprSerializer..ctor(ExtendedActorSystem system)
at Akka.FSharp.Serialization.exprSerializationSupport(ActorSystem system)
I'm using 1.0.4 for Akka/Akka.FSharp and have tried versions 1.2.21 and 1.5.2 of FsPickler
Bartosz Sypytkowski
@Horusiath
@chillitom have you set assembly bindings for FsPickler 1.2 in your app.config?
Joshua Benjamin
@annymsMthd
@Aaronontheweb do the build agents require VS because of the MSTests?
Tom Rathbone
@chillitom
@Horusiath that did the trick, thanks for that
Aaron Stannard
@Aaronontheweb
@annymsMthd yes, and other stuff we're going to use like Code Contracts may depend on it
Aaron Stannard
@Aaronontheweb
@Horusiath I don't know what's changed, but http://petabridge-ci.cloudapp.net/viewLog.html?tab=buildLog&buildTypeId=AkkaNet_AkkaNetPrBuild&buildId=2708&guest=1 is now failing across the board on all PRs
Test collection for Akka.FSharp.Tests.ApiTests (8): Akka.FSharp.Tests (1)
 ApiTests.can serialize and deserialize discriminated unions over remote nodes using wire serializer    

First failure:      1430    #1489    No changes    17 Nov 15 20:37
System.AggregateException : One or more errors occurred.
---- System.AggregateException : One or more errors occurred.
-------- System.Threading.Tasks.TaskCanceledException : A task was canceled.
   at Microsoft.FSharp.Control.AsyncBuilderImpl.commit[a](Result`1 res)
   at Microsoft.FSharp.Control.CancellationTokenOps.RunSynchronously[a](CancellationToken token, FSharpAsync`1 computation, FSharpOption`1 timeout)
   at Microsoft.FSharp.Control.FSharpAsync.RunSynchronously[T](FSharpAsync`1 computation, FSharpOption`1 timeout, FSharpOption`1 cancellationToken)
   at Akka.FSharp.Tests.ApiTests.can serialize and deserialize discriminated unions over remote nodes using wire serializer() in D:\BuildAgent\work\49b164d63843fb4\src\core\Akka.FSharp.Tests\ApiTests.fs:line 76
----- Inner Stack Trace -----
   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
   at Akka.FSharp.Actors.tryCast[Message](Task`1 t) in D:\BuildAgent\work\49b164d63843fb4\src\core\Akka.FSharp\FsApi.fs:line 64
   at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
----- Inner Stack Trace -----
started happening with last night's dev build
Aaron Stannard
@Aaronontheweb
only PR that I pulled in since was @sean-gilliam's XML-DOC PR, which wouldn't affect this
Aaron Stannard
@Aaronontheweb
didn't show up on any individual PRs, but it's appearing inside dev
running it locally to see if I can reproduce, but I can repro it consistently across all three build agents
on different PRs
Stefan Sedich
@stefansedich
my first paket experience is not the best
:facepunch:
Aaron Stannard
@Aaronontheweb
not rebuilding?
Stefan Sedich
@stefansedich
yeah no dice, I wonder if it is this corp network being dodgy
running packet.exe install manually fails trying to get SourceLink.Fake now
Aaron Stannard
@Aaronontheweb
I'll try doing another dev build and wipe out my packages first
Stefan Sedich
@stefansedich
Couldn't get package details for package SourceLink.Fake 1.1.0 on https:
//nuget.org/api/v2.
is what I get
this is probably punishment for being away this long :D
Aaron Stannard
@Aaronontheweb
passed locally... wtf
@stefansedich restored just fine for me - rebuilding it again without any packages
Stefan Sedich
@stefansedich
ok cool, could be my machine or this network
will try again at home
Aaron Stannard
@Aaronontheweb
I'll try a fresh clone
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
Aaron Stannard
@Aaronontheweb
yeah, running fine by the looks of it
must be your network
Stefan Sedich
@stefansedich
yeah k np
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
Bartosz Sypytkowski
@Horusiath
cc @forki
Aaron Stannard
@Aaronontheweb
@stefansedich figured out why my VM images were trashed yesterday, btw
Stefan Sedich
@stefansedich
ah cool what happened?
Aaron Stannard
@Aaronontheweb
TL;DR;
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