No space left on device

[PikaMug]

Describe the bug Similar to #6068 log reports java.io.IOException: No space left on device

To Reproduce Steps to reproduce the behavior:

1. Go to 'https://www.jitpack.io/#PikaMug/Unite/1.1.8'
2. Click on 'Log' for 1.1.8
3. Scroll down to bottom
4. See error

Expected behavior Build success

Screenshots N/A

Additional context

[WARNING] Failed to write tracking file /home/jitpack/.m2/repository/org/apache/maven/scm/maven-scm-api/2.0.0-M1/_remote.repositories
java.io.IOException: No space left on device
    at java.io.RandomAccessFile.writeBytes (Native Method)
    at java.io.RandomAccessFile.write (RandomAccessFile.java:512)
    at org.eclipse.aether.internal.impl.TrackingFileManager.update (TrackingFileManager.java:132)
    at org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.addRepo (EnhancedLocalRepositoryManager.java:184)
    at org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.addArtifact (EnhancedLocalRepositoryManager.java:162)
    at org.eclipse.aether.internal.impl.EnhancedLocalRepositoryManager.add (EnhancedLocalRepositoryManager.java:140)
    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.evaluateDownloads (DefaultArtifactResolver.java:603)
    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads (DefaultArtifactResolver.java:514)
    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve (DefaultArtifactResolver.java:400)
    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts (DefaultArtifactResolver.java:225)
    at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact (DefaultArtifactResolver.java:202)
    at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom (DefaultArtifactDescriptorReader.java:240)
    at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor (DefaultArtifactDescriptorReader.java:171)
    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.resolveCachedArtifactDescriptor (DefaultDependencyCollector.java:530)
    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.getArtifactDescriptorResult (DefaultDependencyCollector.java:515)
    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency (DefaultDependencyCollector.java:403)
    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency (DefaultDependencyCollector.java:356)
    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.process (DefaultDependencyCollector.java:344)
    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.doRecurse (DefaultDependencyCollector.java:498)
    at org.eclipse.aether.internal.impl.collect.DefaultDependencyCollector.processDependency (DefaultDependencyCollector.java:2024-04-19T06:30:23.808512284Z
Exit code: 0

[ascheman]

Is it possible that more builds are affected? I cannot see any builds for some days though I tried to push new/old tags and branches to Github.

[PikaMug]

@ascheman I do not know. The only notable difference between my 1.1.8 build and the previous 1.1.7 is that one dependency is now downloaded from Jitpack instead of a private repository. It also compiles locally without issue.

Unfortunately, this tracker appears to be unmonitored and Jitpack hasn't tweeted in over a year. We may be out of luck.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.