Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing .localnet in artifacts [0.25 XMR] #1268

Closed
Jabster28 opened this issue Sep 10, 2024 · 4 comments
Closed

Missing .localnet in artifacts [0.25 XMR] #1268

Jabster28 opened this issue Sep 10, 2024 · 4 comments
Labels
a:CI About Continuous Integration 💰bounty There is a bounty on this issue

Comments

@Jabster28
Copy link
Contributor

The .localnet artifact has been failing to upload since #1215 was merged in cae360b. There are also some warning in the windows builds that may be related.

@woodser
Copy link
Contributor

woodser commented Sep 11, 2024

This actually appeared with #1244, not #1215.

It causes these annotations in the CI build:

No files were found with the provided path: .localnet. No artifacts will be uploaded..

image

Can anyone help to fix it?

@woodser
Copy link
Contributor

woodser commented Sep 11, 2024

There are also some warning in the windows builds that may be related.

What are the warnings in the windows build?

I only see "OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended".

@Jabster28
Copy link
Contributor Author

@woodser The lines in the log here, but looking at it again those are probably just caching issues and not related.

@woodser woodser added the a:CI About Continuous Integration label Oct 4, 2024
@woodser woodser changed the title Missing .localnet in artifacts Missing .localnet in artifacts [0.25 XMR] Oct 28, 2024
@woodser woodser added the 💰bounty There is a bounty on this issue label Oct 28, 2024
Copy link

There is a bounty on this issue. The amount is in the title. The reward will be awarded to the first person or group of people whose solution is accepted and merged.

In some cases, we may assign the issue to specific contributors. We expect contributors to provide a PR in a reasonable time frame or, in case of an extensive work, updates on their progress. We will unassign the issue if we feel the assignee is not responsive or has abandoned the task.

Read the full conditions and details of our bounty system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:CI About Continuous Integration 💰bounty There is a bounty on this issue
Projects
None yet
Development

No branches or pull requests

2 participants