Disk full for windows GH action

Open Beginner friendly
  • Is something wrong?
#4,396 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
67/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions, java
Domain
build-system, ci-cd

Research direction

Start with .github/workflows/maven_windows.yml and inspect how the workflow places the Jena checkout and runs the Maven build. The issue reports that copying Jena to D: may be an outdated workaround; compare the available drive space and build output sizes shown in the report. Adjust the workflow so the Windows run has sufficient space, then confirm the build completes.

Written by the indexing model from the issue text.

Description

bug
Version

6.3.0-SNAPSHOT

What happened?

Runs of windows GH actions currently fails with disk full, see https://github.com/apache/jena/actions/workflows/maven_windows.yml

Doing a test-run that lists the drives as well as output shows that removing the old workaround of copying jena to the d: drive should solve it, since there is enough available space on the default location d: See df, and output sizes.

Relevant output and stacktrace
Filesystem            Size  Used Avail Use% Mounted on
C:/Program Files/Git  150G  120G   30G  80% /
D:                    150G   34G  117G  23% /d
Largest directories:
560M	/d/a/_temp/m2/repository
1.2G	/d/a/_temp
30G	/d/a/jena/jena
2.0K	/c/Users/runneradmin/.m2
331M	/c/Users/runneradmin/AppData/Local/Temp
328M	/c/Users/runneradmin/AppData/Local/Yarn
851M	/c/Users/runneradmin/AppData/Local/Cypress
Largest target directories:
3.1M	./jena-base/target
6.8M	./jena-ontapi/target
8.2M	./jena-geosparql/target
14M	./jena-fuseki2/jena-fuseki-ui/target
23M	./jena-core/target
42M	./jena-arq/target
45M	./jena-fuseki2/jena-fuseki-geosparql/target
47M	./apache-jena/target
55M	./jena-fuseki2/jena-fuseki-server/target
82M	./jena-db/jena-dboe-base/target
98M	./jena-fuseki2/apache-jena-fuseki/target
581M	./jena-integration-tests/target
1.4G	./jena-fuseki2/jena-fuseki-main/target
3.6G	./jena-tdb2/target
23G	./jena-tdb1/target
Are you interested in making a pull request?

Yes

Dominant language
Java
Stars
1.5k
Forks
733
Avg merge
1d 4h
Merged PRs (30d)
48

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/jena

All issues in apache/jena

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.