paitor

So I've managed to get the code to compile and install on windows but it seems all tests fails meaning that something is broken on windows. I do not have...

So I resorted to use github to try to debug the win build, question though. Is there a way to temporarily turn of some of the checks to speed things...

Thanks, I'll have a look at it. Will probably have to put this aside for two weeks now though (upcoming meeting, NGWM, and some work to do prior to that...

@megies Sure will do, at least I've narrowed down the issue to that the windows build by some reason is only reading the first block in the gcf-files so presumably...

The failing build for ubuntu-latest, py3.8 is a bit of surprise though, have not seen this before.

@megies Finally got hold of a windows can and fixed the remaining issues. The remaining failing tests on windows are related to io.segy (Extended textual headers are not yet supported)...

Failing tests seems unrelated.

@megies Guess you are quite busy but bumping this again as it would be nice to finish it of before the release of obspy 1.4. The remaining failing test seems...

@megies Sure, just so I get it right though, the commands to run would then be: git fetch master git checkout gcf-c-source git rebase master or? (sorry never done this...

@megies Another newbie question here, how do I figure out the name of the main repo? When I originally cloned a fork of obspy I ran $ git clone https://github.com/paitor/obspy.git...