fsharp build fails on ppc64le

[Sapana-Khemkar]

while doing source build using dotnet8 preview7 fsharp build fails with below error

> /builddir/build/BUILD/dotnet-v8.0.0-preview.7.23375.6-x64-bootstrap/src/fsharp/artifacts/source-build/self/src/src/Compiler/TypedTree/TypedTreePickle.fsi(1,1): error FS0240: The signature file 'TypedTreePickle' does not have a corresponding implementation file. If an implementation file exists then check the 'module' and 'namespace' declarations in the signature and implementation files match. [/builddir/build/BUILD/dotnet-v8.0.0-preview.7.23375.6-x64-bootstrap/src/fsharp/artifacts/source-build/self/src/src/Compiler/FSharp.Compiler.Service.fsproj::TargetFramework=netstandard2.0] 0 Warning(s) 1 Error(s)

cc: tmds omajid

[vzarytovskii]

Well, that's new. Wondering why would platform matter, we shouldn't be doing anything platform-dependent...I hope.

[vzarytovskii]

It seems like something went wrong when fetching/copying files, since it cannot find a corresponding .fs file. cc @MichaelSimons , do you know what would be the easiest way of troubleshooting it?

also, @Sapana-Khemkar does the build work if you clone this repo (not source build one), and run build script?

[Sapana-Khemkar]

It seems like something went wrong when fetching/copying files, since it cannot find a corresponding .fs file. cc @MichaelSimons , do you know what would be the easiest way of troubleshooting it?

also, @Sapana-Khemkar does the build work if you clone this repo (not source build one), and run build script?

Have not tried independent build. But even source build works sometime and gives this error in between.

[vzarytovskii]

It seems like something went wrong when fetching/copying files, since it cannot find a corresponding .fs file. cc @MichaelSimons , do you know what would be the easiest way of troubleshooting it?
also, @Sapana-Khemkar does the build work if you clone this repo (not source build one), and run build script?

Have not tried independent build. But even source build works sometime and gives this error in between.

That doesn't sound right. It sounds like the file is getting deleted or locked.

[MichaelSimons]

@MichaelSimons , do you know what would be the easiest way of troubleshooting it?

My initial suggestion is to start with the binlog. @Sapana-Khemkar - can you share the binlog?

[Sapana-Khemkar]

@MichaelSimons @vzarytovskii
We did further analysis and found that issue is observed only on CentOS stream 8. It seems this failure is something on the RPM/RHEL side to fix. Hence closing this issue.