-
Notifications
You must be signed in to change notification settings - Fork 68
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
GToolkit - Add as Supported Platform #589
Conversation
seandenigris
commented
Feb 27, 2023
- first pass on GToolkit - Add as Platform #544 that downloads GT, loads a project, and runs its tests
- several hardcoded values
- needs cleaning
- first pass that downloads GT, loads a project, and runs its tests - several hardcoded values - needs cleaning
- Supports latest release only
Can someone resend me an invite to the repo? I accepted but it had already expired. Also, I tested this locally, but would someone more familiar with StCI internals have a look and see if it all makes sense? cc/ @fniephaus @girba |
What kind of access do you need to the repo and what for?
Seems ok so far. There's no point in running the tests though because you didn't add a GToolkit job to the build matrix. Can you do that please? |
Ha ha, don't know. Someone (I think you) had sent me an invitation which expired, so I thought maybe that was important, especially when I noticed I could not trigger CI on my PR without access. Since unfortunately it looks like I will be the GT support maintainer, whatever access level you think would be appropriate for that role, if any.
Sure, Any guidance on how to do that? |
Edit |
Okay, done |
It's unfortunate you think this is unfortunate. 😉 Once you've contributed a PR, the tests will run automatically for your PRs and you can always run the tests in your fork. So for the time being, I don't see why you'd need any additional permissions, unless you want to maintain more than the GT integration. 😅 |
I just triggered the builds for this PR and then this happens. 🤷 |
It's unfortunate you think this is unfortunate. 😉
Ha ha just being dramatic. No big deal
Once you've contributed a PR, the tests will run automatically for your PRs and you can always run the tests in your fork.
Aha. Okay. Running the test for my PR was the issue, so that’s good news.
So for the time being, I don't see why you'd need any additional permissions, unless you want to maintain more than the GT integration. 😅
Sounds like we’re all good then
|
Looks like it’s resolved |
8b017c2
to
191e3d4
Compare
Since you complained about writing some Bash, I took care of the JavaScript part for all of this: Nonetheless, there is a test failure:
https://github.com/hpi-swa/smalltalkCI/actions/runs/4321917736/jobs/7543790478#step:4:1352 |
Ha ha thanks. See sometimes complaining works
I’m not sure how to fix that. I reported it on GT’s Discord. Hopefully someone at feenk will weigh in |
Per @chisandrei on GT Discord:
The issue for the above mentioned graphical stack pass is feenkcom/gtoolkit#3107 In the meantime, I can have a look. Any tips for how I might easily reproduce this locally? |
feenkcom/gtoolkit#3107 is closed. @fniephaus can you rerun the CI/tests? Perhaps we’ll get a better result! |
Clone the smalltalkCI repo and run what runs on GitHub Actions: smalltalkCI/.github/workflows/main.yml Line 80 in 5642d38
Add --headfull for access to the UI.
Sure, but unfortunately still failing. |
I wouldn't mind skipping the test when running on GToolkit. |
I've disabled the test on GToolkit and renamed |
Thanks! Yes I’d like to start using this and we can evolve as needed |