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

Update versions in #beautifulComments, #documentBrowser and #welcomeBrowser for BaselineOfPharo for Pharo 11 to ‘v1.0.1’, ‘v1.0.3’ and ‘v1.0.2’ #17427

Merged
merged 3 commits into from
Nov 26, 2024

Conversation

Rinzwind
Copy link
Contributor

@Rinzwind Rinzwind commented Nov 23, 2024

This pull request updates the versions in #documentBrowser and #welcomeBrowser for BaselineOfPharo for Pharo 11 to ‘v1.0.3’ and ‘v1.0.2’ respectively. The tags need to be added first, I cannot do that; for NewTools-DocumentBrowser, ‘v1.0.3’ should refer to commit 7d3996762a13, and for NewTools-WelcomeBrowser, ‘v1.0.2’ should refer to commit ed5c5339466e.

@Rinzwind Rinzwind changed the title Update versions in #documentBrowser and #welcomeBrowser for BaselineOfPharo to ‘v1.0.3’ and ‘v1.0.2’ Update versions in #documentBrowser and #welcomeBrowser for BaselineOfPharo for Pharo 11 to ‘v1.0.3’ and ‘v1.0.2’ Nov 23, 2024
@Ducasse
Copy link
Member

Ducasse commented Nov 23, 2024

Tx Kris

@Ducasse
Copy link
Member

Ducasse commented Nov 23, 2024

I'm trying to create a tag but with the GH UI so far I failed. I will check if I can do that on the command line.

@Ducasse
Copy link
Member

Ducasse commented Nov 23, 2024

I pushed the two tags.

@Ducasse Ducasse closed this Nov 23, 2024
@Ducasse Ducasse reopened this Nov 23, 2024
@Ducasse
Copy link
Member

Ducasse commented Nov 23, 2024

So now rechecking the build

@Ducasse
Copy link
Member

Ducasse commented Nov 23, 2024

Looks like the there is a problem:

MetacelloNotification: Fetched -> (nearest) BaselineOfClap-tonel.1 --- tonel:///builds/workspace/est_and_branch_Pipeline_PR-17427/64/src --- tonel:///builds/workspace/est_and_branch_Pipeline_PR-17427/64/src
MetacelloNotification: Loading -> BaselineOfClap-tonel.1 --- tonel:///builds/workspace/est_and_branch_Pipeline_PR-17427/64/src --- tonel:///builds/workspace/est_and_branch_Pipeline_PR-17427/64/src
MetacelloNotification: Loaded -> BaselineOfClap-tonel.1 --- tonel:///builds/workspace/est_and_branch_Pipeline_PR-17427/64/src --- tonel:///builds/workspace/est_and_branch_Pipeline_PR-17427/64/src
MetacelloNotification: ...RETRY->BaselineOfWelcomeBrowser
MetacelloNotification: ...RETRY->BaselineOfWelcomeBrowser
�[31mFileDoesNotExistException: '/tmp/github--pharospecNewToolsWelcomeBrowserv102265660148051765068214940904136247704441.zip'
�[0mFile>>openForWrite:
File>>openForRead
File>>readStream
FileHandle>>binaryReadStream
FileSystem>>binaryReadStreamOn:
FileReference>>binaryReadStream
ZipArchive>>readFrom:
MetacelloPharo30Platform(MetacelloPharoPlatform)>>downloadZipArchive:to:
MCGitHubRepository class(MCGitBasedNetworkRepository class)>>projectDirectoryFrom:version:
MCGitHubRepository(MCGitBasedNetworkRepository)>>calculateRepositoryDirectory
MCGitHubRepository(MCGitBasedNetworkRepository)>>resolveLocalRespository
MCGitHubRepository(MCGitBasedNetworkRepository)>>ensureLocalRepository
MCGitHubRepository(MCGitBasedNetworkRepository)>>localRepository
MCGitHubRepository(MCGitBasedNetworkRepository)>>goferReferences

@Ducasse
Copy link
Member

Ducasse commented Nov 23, 2024

Ah but I'm also confused because it should be for Pharo 11 so I do not know how this build can show us anything.

@Rinzwind
Copy link
Contributor Author

Thanks! There was no new build though because Jenkins didn’t process the ‘REMOVED event’ before you had reopened the pull request, see the following from the ‘Multibranch Pipeline Events’ log, and the example from the log I gave in pull request #16172:

[Sat Nov 23 17:33:18 CET 2024] Received Pull request #17427 closed […] REMOVED event […] with timestamp Sat Nov 23 17:33:13 CET 2024
[…]
No changes detected: PR-17427 […]
[…]
[Sat Nov 23 17:33:20 CET 2024] Received Pull request #17427 reopened […] UPDATED event […] with timestamp Sat Nov 23 17:33:15 CET 2024
[…]
No changes detected: PR-17427 […]

@Rinzwind Rinzwind closed this Nov 23, 2024
@Rinzwind Rinzwind reopened this Nov 23, 2024
@Rinzwind
Copy link
Contributor Author

I’m guessing the error in build 2 is due to BaselineOfBeautifulComments referring to ‘master’ for Microdown. I added commit b6d150f and opened a pull request for that: BeautifulComments pull request #49.

@Rinzwind Rinzwind changed the title Update versions in #documentBrowser and #welcomeBrowser for BaselineOfPharo for Pharo 11 to ‘v1.0.3’ and ‘v1.0.2’ Update versions in #beautifulComments, #documentBrowser and #welcomeBrowser for BaselineOfPharo for Pharo 11 to ‘v1.0.1’, ‘v1.0.3’ and ‘v1.0.2’ Nov 24, 2024
@tesonep
Copy link
Collaborator

tesonep commented Nov 26, 2024

Hi @Rinzwind thanks so much for the PR, I will see what is happening to help you with this

@jecisc
Copy link
Member

jecisc commented Nov 26, 2024

I do not see any v1.0.1 tag in Beautiful comments.

https://github.com/pillar-markup/BeautifulComments/tags

GitHub
A nice extension of Pharo to support class comments in Microdown and better rendered. - Tags · pillar-markup/BeautifulComments

@jecisc
Copy link
Member

jecisc commented Nov 26, 2024

I just released it.

https://github.com/pillar-markup/BeautifulComments/releases/tag/v1.0.1

I'll restart the CI

GitHub
What's Changed

Make BaselineOfBeautifulComments for Pharo 11 use the tag ‘v2.4.1’ instead of the branch ‘master’ for Microdown by @Rinzwind in #49

New Contributors

@Rinzwind made their first con...

@Rinzwind
Copy link
Contributor Author

Ok, thanks! I’m afraid I don’t understand the error on Windows in build 6, I’ll try starting another one.

@Rinzwind Rinzwind closed this Nov 26, 2024
@Rinzwind Rinzwind reopened this Nov 26, 2024
@Rinzwind
Copy link
Contributor Author

Build 7 seems to have the same error(s) on Windows:

+ ./pharo Pharo.image test --junit-xml-output --stage-name=Tests-windows-64 '.*'
[ERROR] 2024-11-26 18:48:54.000 sqMakeMemoryNotExecutableFromTo (extracted/vm/src/win/sqWin32SpurAlloc.c:226):VirtualProtect(x,y,PAGE_EXECUTE_READWRITE): No error
Running tests in 759 Packages
[…]
PrimitiveFailed: primitive #primitivePerformWorkerCall:withArguments: in TFSameThreadRunner failed
TFSameThreadRunner(ProtoObject)>>primitiveFailed:
[…]
AthensCairoSurface class>>destroySurfaceHandle:
[…]
FFIExternalResourceExecutor>>finalize

@jecisc
Copy link
Member

jecisc commented Nov 26, 2024

This PR allows the image to build even of the windows tests are broken. I'll merge

@jecisc jecisc merged commit d556a4f into pharo-project:Pharo11 Nov 26, 2024
1 of 2 checks passed
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.

4 participants