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

GToolkit - Add as Supported Platform #589

Merged
merged 6 commits into from
Apr 11, 2023

Conversation

seandenigris
Copy link
Contributor

- first pass that downloads GT, loads a project, and runs its tests
- several hardcoded values
- needs cleaning
- Supports latest release only
@seandenigris seandenigris changed the title GToolkit Platform Spike - Not Ready to Merge GToolkit - Add as Supported Platform Mar 1, 2023
@seandenigris
Copy link
Contributor Author

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

@fniephaus
Copy link
Member

Can someone resend me an invite to the repo?

What kind of access do you need to the repo and what for?

I tested this locally, but would someone more familiar with StCI internals have a look and see if it all makes sense?

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?

run.sh Outdated Show resolved Hide resolved
gtoolkit/run.sh Show resolved Hide resolved
gtoolkit/run.sh Outdated Show resolved Hide resolved
@seandenigris
Copy link
Contributor Author

What kind of access do you need to the repo and what for?

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.

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?

Sure, Any guidance on how to do that?

@gcotelli
Copy link
Collaborator

gcotelli commented Mar 2, 2023

What kind of access do you need to the repo and what for?

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.

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?

Sure, Any guidance on how to do that?

Edit .github/workflows/main.yml in your branch and add the GToolkit variants to the build matrix.

@seandenigris
Copy link
Contributor Author

Edit .github/workflows/main.yml in your branch and add the GToolkit variants to the build matrix.

Okay, done

@fniephaus
Copy link
Member

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.

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. 😅

@fniephaus
Copy link
Member

I just triggered the builds for this PR and then this happens. 🤷

@seandenigris
Copy link
Contributor Author

seandenigris commented Mar 3, 2023 via email

@seandenigris
Copy link
Contributor Author

seandenigris commented Mar 3, 2023

I just triggered the builds for this PR and then this happens. 🤷

Looks like it’s resolved

@fniephaus
Copy link
Member

Since you complained about writing some Bash, I took care of the JavaScript part for all of this:
hpi-swa/setup-smalltalkCI@4d1933c.

Nonetheless, there is a test failure:

SmalltalkCIPharoTest
 ✗ #testPromptToProceed (5506ms)
SubclassResponsibility: RustWindowingWorldRenderer class had the subclass responsibility to implement #isApplicableFor:
RustWindowingWorldRenderer class(Object)>>subclassResponsibility
RustWindowingWorldRenderer class(AbstractWorldRenderer class)>>isApplicableFor:
[ :aClass | aClass isApplicableFor: aWorld ] in AbstractWorldRenderer class>>detectCorrectOneForWorld:
[ :each | 
			(aBlock value: each)
				ifTrue: [ ^ foundBlock cull: each ] ] in OrderedCollection(Collection)>>detect:ifFound:ifNone:
OrderedCollection>>do:
OrderedCollection(Collection)>>detect:ifFound:ifNone:
OrderedCollection(Collection)>>detect:ifFound:
AbstractWorldRenderer class>>detectCorrectOneForWorld:
MorphicUIManager>>activate
UIManager class>>default:
SmalltalkCIPharoTest>>testPromptToProceed ...default: MorphicUIManager new
SCICoverageWrapper>>run:with:in:
SmalltalkCIPharoTest(Object)>>perform:
SmalltalkCIPharoTest(TestCase)>>performTest

https://github.com/hpi-swa/smalltalkCI/actions/runs/4321917736/jobs/7543790478#step:4:1352

@seandenigris
Copy link
Contributor Author

seandenigris commented Mar 3, 2023

Since you complained about writing some Bash, I took care of the JavaScript part for all of this

Ha ha thanks. See sometimes complaining works

Nonetheless, there is a test failure:

I’m not sure how to fix that. I reported it on GT’s Discord. Hopefully someone at feenk will weigh in

@seandenigris
Copy link
Contributor Author

seandenigris commented Mar 4, 2023

Nonetheless, there is a test failure:
SmalltalkCIPharoTest
✗ #testPromptToProceed (5506ms)

Per @chisandrei on GT Discord:

Right at moment we are doing a larger pass on the graphical stack for linux. Not sure if this error is related, but should be easier to debug after that pass is done

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?

@seandenigris
Copy link
Contributor Author

feenkcom/gtoolkit#3107 is closed. @fniephaus can you rerun the CI/tests? Perhaps we’ll get a better result!

@fniephaus
Copy link
Member

Any tips for how I might easily reproduce this locally?

Clone the smalltalkCI repo and run what runs on GitHub Actions:

bin/smalltalkci -s ${{ matrix.smalltalk }} --self-test

Add --headfull for access to the UI.

can you rerun the CI/tests? Perhaps we’ll get a better result!

Sure, but unfortunately still failing.

@fniephaus
Copy link
Member

I wouldn't mind skipping the test when running on GToolkit.

@fniephaus
Copy link
Member

I've disabled the test on GToolkit and renamed GToolkit-release to GToolkit64-release. If you like, we can merge this now.

@seandenigris
Copy link
Contributor Author

Thanks! Yes I’d like to start using this and we can evolve as needed

@fniephaus fniephaus merged commit f0dbb2e into hpi-swa:master Apr 11, 2023
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