apache / apache/livy

Master doesnt build and there is no release tag for last release

Open
#499 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Scala
Stars
963
Forks
625
Avg merge
6d 21h
Merged PRs (30d)
6

Description

```
[INFO] Total time: 24.519 s
[INFO] Finished at: 2025-12-02T10:22:56-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project livy-server: Could not resolve dependencies for project org.apache.livy:livy-server:jar:0.10.0-incubating-SNAPSHOT
[ERROR] dependency: org.apache.livy:livy-core_2.12:jar:tests:0.10.0-incubating-SNAPSHOT (test)
[ERROR] org.apache.livy:livy-core_2.12:jar:tests:0.10.0-incubating-SNAPSHOT was not found in https://repository.apache.org/snapshots during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of apache.snapshots has elapsed or updates are forced
[ERROR]
[ERROR] -> [Help 1]
[ERROR]

````
```
edward@fedora:~/incubator-livy$ git tag -l
v0.2.0
v0.3.0
v0.4.0-incubating
v0.5.0-incubating
v0.6.0-incubating
v0.6.0-incubating-rc1
v0.6.0-incubating-rc2
v0.7.0-incubating
v0.7.0-incubating-rc1
v0.7.0-incubating-rc2
v0.7.0-incubating-rc3
v0.7.0-incubating-rc4
v0.7.1-incubating-rc1
v0.8.0-incubating
v0.8.0-incubating-rc1
v0.8.0-incubating-rc2
```

commit 0efa2d7e508c6d955cebe48a5159ffc3202e57a1 (HEAD -> master, origin/master, origin/HEAD)
Author: Arnav Balyan <60175178+ArnavBalyan@users.noreply.github.com>
Date: Tue Dec 2 01:27:42 2025 +0530

[LIVY-1022][TEST] Update NM Disk utilization percentage for UT

## What changes were proposed in this pull request?

* Currently Livy UT for `JobApiIT.scala` fails due to disk being 92% which causes the node to be lost.
* Updated this to 100% for the UT to ensure the tests pass even if the disk utilization is over 90%
* Closes LIVY-1022

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the reported master build failure and checking the repository's release and tag state. Inspect the dependency-resolution error for livy-core_2.12 and compare the available tags with the expected last release. Done means master builds successfully and the missing release tag or its cause is resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, scala
Domain
build-system, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.