Skip to content

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

@edwardcapriolo

Description

@edwardcapriolo
[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 0efa2d7 (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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions