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

Support arguments and working directory in launching Core Build proje… #821

Merged
merged 2 commits into from
Sep 12, 2024

Conversation

ewaterlander
Copy link
Contributor

…cts for Local

Added the CArgumentsTab to the Core Build launch configuration for the Local target. This enables users to set command line arguments and specify a working directory.

…cts for Local

Added the CArgumentsTab to the Core Build launch configuration for the
Local target. This enables users to set command line arguments and
specify a working directory.
@ewaterlander
Copy link
Contributor Author

image

@ewaterlander
Copy link
Contributor Author

Hi @betamaxbandit ,
would you like to review?

@ewaterlander
Copy link
Contributor Author

Note this fixes all 4 flavors of Core Build projects: CMake, Makefile, Autotools, Arduino.

@betamaxbandit
Copy link
Contributor

Hi @ewaterlander ,
Yes I'll review this. Hopefully will get to it soon.
Cheers John

@ewaterlander
Copy link
Contributor Author

Hi @ewaterlander , Yes I'll review this. Hopefully will get to it soon. Cheers John

Thanks!
I think the failing tests are not caused by my change. I see no relation. I think these failures are caused by timeouts.

@jonahgraham
Copy link
Member

Please see #816 the test fails are not caused by your change, but rather by some change on the GitHub runners.

@ewaterlander
Copy link
Contributor Author

Should I trigger a new build?
What's actually the best way to do that? What I would do now is a git amend with a small change of the commit message and then a push -f.

@betamaxbandit
Copy link
Contributor

Should I trigger a new build? What's actually the best way to do that? What I would do now is a git amend with a small change of the commit message and then a push -f.

Hi @ewaterlander ,
yes that's what I did the other day for mine.

@ewaterlander
Copy link
Contributor Author

Build is still broken.

@jonahgraham
Copy link
Member

I re triggered the licensing check, the 8 errors/60 fails is #816

Copy link
Contributor

@betamaxbandit betamaxbandit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ewaterlander
Copy link
Contributor Author

Hi,
Is merging on hold? What should I do?

@betamaxbandit
Copy link
Contributor

Hi, Is merging on hold? What should I do?

Hi @ewaterlander ,
I also have some patches which I'm waiting to be merged, so I expect @jonahgraham may be away on vacation.

Cheers John

@ewaterlander
Copy link
Contributor Author

I retriggerd a build. I hope this PR can get merged soon.

@ewaterlander
Copy link
Contributor Author

I retriggerd a build. I hope this PR can get merged soon.

Build failed with these errors:

Error: Failed to resolve target definition file:/work/releng/org.eclipse.cdt.target/cdt.target: Failed to load p2 metadata repository from location https://download.eclipse.org/eclipse/updates/4.33-I-builds/: No repository found at https://download.eclipse.org/eclipse/updates/4.33-I-builds.
Error:
Error: To see the full stack trace of the errors, re-run Maven with the -e switch.
Error: Re-run Maven using the -X switch to enable full debug logging.

@jonahgraham jonahgraham merged commit 36abcce into eclipse-cdt:main Sep 12, 2024
2 of 4 checks passed
@ewaterlander ewaterlander deleted the arguments branch September 13, 2024 09:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants