Use Buck from Jitpack

[cortinico]

I'm updating the Buck version + switching to use the version from Jitpack:
https://jitpack.io/#facebook/buck/v2022.05.05.01

I've realized we hava a -java11.pex file we can use and should work fine with Java11 so there is no need to build Buck from source anymore.

[cortinico]

@gengjiawen it seems like build is "skipped" due to:

System.IO.IOException: No space left on device : '/home/runner/runners/2.295.0/_diag/Worker_20220818-111350-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan1 buffer, Int64 fileOffset) at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite() at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id) at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message) at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message) at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args) System.IO.IOException: No space left on device : '/home/runner/runners/2.295.0/_diag/Worker_20220818-111350-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan1 buffer, Int64 fileOffset) at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite() at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id) at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message) at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message) at GitHub.Runner.Common.Tracing.Error(Exception exception) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args) Unhandled exception. System.IO.IOException: No space left on device : '/home/runner/runners/2.295.0/_diag/Worker_20220818-111350-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset) at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite() at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at System.Diagnostics.TraceSource.Flush() at GitHub.Runner.Common.TraceManager.Dispose(Boolean disposing) at GitHub.Runner.Common.TraceManager.Dispose() at GitHub.Runner.Common.HostContext.Dispose(Boolean disposing) at GitHub.Runner.Common.HostContext.Dispose() at GitHub.Runner.Worker.Program.Main(String[] args)

Have you ever experienced something similar?

[gengjiawen]

Yeap:

f4c196f (#169)

My case is running test case.

[cortinico]

Yeap:

f4c196f (#169)

My case is running test case.

Awesome will try this 👍 Thanks for the suggestion

[cortinico]

Nope no luck. Also unsure why this is the case 🤔 as we should be using less spaces with my changes.

[gengjiawen]

Nope no luck. Also unsure why this is the case 🤔 as we should be using less spaces with my changes.

Yeap. Looks like a upstream bug or new limitation from github action for me.

[gengjiawen]

Another worth try is revert cmdlines https://github.com/react-native-community/docker-android/pull/175/files.

It's the only related change. (It works on circleCI)

[gengjiawen]

Also leotm/react-native-template-new-architecture#918 (comment)

[leotm]

i thought about maximising build space at first too after mini freakout suddenly all PR's failing 😆 but knew had to be smth bigger

thx @gengjiawen again for cross-referencing and code review

22.04 fixed it for me, so now rebasing/re-trying all PR's w renovate (should hopefully be passing again as usual in couple/few hrs)

[cortinico]

@gengjiawen I had to move the build step to CircleCI as the Github Runner was too much constrained. Now all is green. Are we fine merging this?

[gengjiawen]

@gengjiawen I had to move the build step to CircleCI as the Github Runner was too much constrained. Now all is green. Are we fine merging this?

Yeap.