You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm fairly new to go so help me out if I'm completely in left field on this one.
Running a plain go test on a clean windows install of gosigar fails. I believe that this is due to platform differences between windows and *nix systems that are not accounted for in the sigar_interface_test.go and the concrete_sigar_test.go outlined in detail in this pull request: /pull/13
One example is that executables in windows need a ".exe" suffix whereas in a *nix system this need not be the case
Apologies for the rough cmd window formatting :)
←[90mC:/Projects/GoWorkspace/src/github.com/elastic/gosigar/sigar_interface_
test.go:100←[0m
←[91mExpected
<[]string | len:2, cap:2>: ["go", "ginkgo"]
to contain element matching
<string>: go.exe←[0m
Perhaps an appveyor + travis CI server would help illuminate these types of issues by building and running tests on all environments gosigar is deployed :)
The text was updated successfully, but these errors were encountered:
Howdy!
I'm fairly new to go so help me out if I'm completely in left field on this one.
Running a plain
go test
on a clean windows install of gosigar fails. I believe that this is due to platform differences between windows and *nix systems that are not accounted for in thesigar_interface_test.go
and theconcrete_sigar_test.go
outlined in detail in this pull request: /pull/13One example is that executables in windows need a ".exe" suffix whereas in a *nix system this need not be the case
Apologies for the rough cmd window formatting :)
Perhaps an appveyor + travis CI server would help illuminate these types of issues by building and running tests on all environments gosigar is deployed :)
The text was updated successfully, but these errors were encountered: