### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [August 25, 2018, 4:09pm UTC](https://discourse.paraview.org/t/pvbinsdash-gfortran-internal-compiler-error/475/1 "2018-08-25T16:09:58Z")
Some gfortran compiler errors started showing up August 23 [[CDash link](https://open.cdash.org/index.php?project=ParaView&date=2018-08-23)] on pvbinsdaash. Only one commit (and subsequent merge) is different in the superbuild between the passing and failing test.
```nohighlight
commit 78206458e7a2f4148ef6dbcfdb2e53e1789c27eb
Author: Cory Quammen
Date: Mon Aug 13 23:44:55 2018 -0400
Rename example data directory
Changed from "data" to "examples".
```
ParaView has a number of changes, but none affecting BLAS (BLAS is an external dependency anyhow).
The same version of BLAS is used in the passing and failing tests, so I’m wondering @shawn.waldon if gfortran was updated/changed on pvbinsdash?
---
### Author:  [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [August 27, 2018, 12:43pm UTC](https://discourse.paraview.org/t/pvbinsdash-gfortran-internal-compiler-error/475/2 "2018-08-27T12:43:27Z")
I was looking at it on Friday and will continue to look today. Will keep you posted. We tried the obvious things, like rebooting etc already to no avail.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [August 27, 2018, 12:44pm UTC](https://discourse.paraview.org/t/pvbinsdash-gfortran-internal-compiler-error/475/3 "2018-08-27T12:44:19Z")
Cool, thanks.
---
### Author:  [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [August 27, 2018, 2:39pm UTC](https://discourse.paraview.org/t/pvbinsdash-gfortran-internal-compiler-error/475/4 "2018-08-27T14:39:28Z")
nothing obvious is jumping out. Not sure what changed. even going back to a version that previously worked causes the failure. Guess we’ll wait till Ben is back end of this week.
---
### Author:  [@shawn.waldon](https://discourse.paraview.org/u/shawn.waldon)
#### Post date: [August 27, 2018, 2:44pm UTC](https://discourse.paraview.org/t/pvbinsdash-gfortran-internal-compiler-error/475/5 "2018-08-27T14:44:11Z")
> [@cory.quammen](#):
>
> if gfortran was updated/changed on pvbinsdash?
As far as I can tell nothing changed between the last passing build and the first failing one. `pvbinsdash` is a docker image, so it should have stayed the same. Utkarsh and I (and Rob I think) are the only ones with access to that machine and we didn’t change anything.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [August 27, 2018, 2:56pm UTC](https://discourse.paraview.org/t/pvbinsdash-gfortran-internal-compiler-error/475/6 "2018-08-27T14:56:39Z")
> [@utkarsh.ayachit](#):
>
> Guess we’ll wait till Ben is back end of this week.
What a welcome home 🎁!
> [@shawn.waldon](#):
>
> Utkarsh and I (and Rob I think) are the only ones with access to that machine and we didn’t change anything.
I’ll vote for a cosmic ray flipping a bit somewhere.
---
### Author:  [@Dave\_DeMarle](https://discourse.paraview.org/u/Dave_DeMarle)
#### Post date: [August 29, 2018, 2:54pm UTC](https://discourse.paraview.org/t/pvbinsdash-gfortran-internal-compiler-error/475/7 "2018-08-29T14:54:27Z")
They were running a bunch of tests at the LHC that might be responsible too. 😉