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

openjdk 15.0.2 #69460

Closed
wants to merge 4 commits into from
Closed

Conversation

el7cosmos
Copy link
Contributor

Created with brew bump-formula-pr.

resource blocks may require updates.

Formula/openjdk.rb Outdated Show resolved Hide resolved
Formula/openjdk.rb Outdated Show resolved Hide resolved
@carlocab
Copy link
Member

carlocab commented Jan 21, 2021

@carlocab
Copy link
Member

carlocab commented Jan 21, 2021

All three Intel CI nodes:

Error: An exception occurred within a child process:
  RuntimeError: cannot find build number in .hg_archival.txt

These are the contents of .hg_archival.txt:

repo: fd16c54261b32be1aaedd863b7e856801b7f8543
node: 465ac9b408cae3e98c4f4630d22e653e725187ae
branch: default
tag: jdk-15.0.2-ga

Looks like the build number is no longer available here.

build = File.read(".hg_archival.txt")
.scan(/^tag: jdk-#{version}\+(.+)$/)
.map(&:first)
.map(&:to_i)
.max
raise "cannot find build number in .hg_archival.txt" if build.nil?

@carlocab
Copy link
Member

For openjdk 15.0.1, this is the content of .hg_archival.txt:

repo: fd16c54261b32be1aaedd863b7e856801b7f8543
node: d9b7c07593100c3cae95238999f972ceb0ff067c
branch: default
tag: jdk-15.0.1+9
tag: jdk-15.0.1-ga

This gives the build number 9. If we had used the same scheme as ARM to parse the build number from .hgtags, we'd have gotten 8:

❯ tail -10 .hgtags
e3f940bd3c8fcdf4ca704c6eb1ac745d155859d5 jdk-15+36
93813843680bbe1b7efbca56c03fd137f20a2c31 jdk-15.0.1+0
286ddf41c3f697bcf684042544fa4736ba1b85f3 jdk-15.0.1+1
08e8fa30d8456913dd0f698f9c61e4adac22805a jdk-15.0.1+2
99d9a174da61ca1e359638170b47a7ddc9cc77d5 jdk-15.0.1+3
72cddf95705e758aea928e025694e445af844d1f jdk-15.0.1+4
ac7b0cbc8dac94ff225021d2786efbad2326b037 jdk-15.0.1+5
a90f4378bf70eb17e8a8322aa0b94a4c6c923932 jdk-15.0.1+6
23fd169be90a803fef99776afefa3072189980be jdk-15.0.1+7
8dd4d8eaf0de32a79d1f48c3421e5666d75beff9 jdk-15.0.1+8

@SMillerDev
Copy link
Member

Why do we need to have the build number?

If it's useful I guess we could move to the arm way (since that's where they seem to be going)

@carlocab
Copy link
Member

Why do we need to have the build number?

No idea.

we could move to the arm way

That would've given a build number of 8 instead of 9 for 15.0.1 though: #69460 (comment) Not sure if that's important at all.

@jonchang
Copy link
Contributor

It "should" be +8. Usually they have two tags pointing to a single commit like so:

e3f940bd3c8fcdf4ca704c6eb1ac745d155859d5 jdk-15+36
e3f940bd3c8fcdf4ca704c6eb1ac745d155859d5 jdk-15-ga

for some reason upstream has not done it this time. We could potentially wait for adoptopenjdk to release 15.0.2 to see what build number they pick.

@jonchang
Copy link
Contributor

jonchang commented Jan 21, 2021

Why do we need to have the build number?

If it's useful I guess we could move to the arm way (since that's where they seem to be going)

Let's just go with this since it's easier. I think build numbers are really only used when comparing among the same java patch version and I think it's a legacy of openjdk 8-era java versioning (like jdk8u282)

@carlocab
Copy link
Member

Let's just go with this since it's easier.

Done. This is still slightly different from ARM, which uses only the major version, though. However, I assume that's because .hgtags in the ARM tarball only contains lines with the major version (unlike the 15.0.2 tarball).

@carlocab
Copy link
Member

carlocab commented Jan 21, 2021

Same error; still can't find the build number. (I forgot to change the error message to .hgtags.) Not sure why; these are the relevant lines in .hgtags:

❯ tail -8 .hgtags
1613004c47e9dc867a2c2c43d716533b1aaedc5f jdk-15.0.2+0
cc4fdb537bc14734064a9a8eadb091fd1c12b36e jdk-15.0.2+1
d24e907486b3f90691980b0dde01efca5840abc6 jdk-15.0.2+2
dbb11e11955ad1240ba775ab0007a14547e14ce6 jdk-15.0.2+3
4c4a2eb7b19ecb31620e6bb120e40f8a5fd1737a jdk-15.0.2+4
e431a9461b1356c4b763443e5333b3f4a8695eaf jdk-15.0.2+5
d5977ee56509ceaa3d3c8e1aebbca76651358da4 jdk-15.0.2+6
38912b2a5bcb396c75f8707e300773c874327451 jdk-15.0.2+7

Ah, I see. I forgot to remove the ^ from the regex.

@carlocab carlocab force-pushed the bump-openjdk-15.0.2 branch 2 times, most recently from 2c8baf8 to 9bdad7e Compare January 21, 2021 09:18
@carlocab
Copy link
Member

Re the build number: #68946 (comment)

It seems we should add one to it on Intel? (I'm not even sure how important this is.)

@carlocab
Copy link
Member

ARM CI broken by Homebrew/brew#10375.

Error: Invalid usage: not (yet) working on Apple Silicon!

@carlocab
Copy link
Member

Big Sur

Error: 12 failed steps!
brew test --retry --verbose byteman
brew install --build-from-source emscripten
brew test --retry --verbose fits
brew test --retry --verbose jasmin
brew test --retry --verbose jetty
brew install --build-from-source languagetool
brew install --build-from-source man-db
brew install --build-from-source mesos
brew test --retry --verbose nexus
rm -rf /Users/brew/Library/Caches/Homebrew
brew install --build-from-source planck
brew install --build-from-source simutrans

Catalina

Error: 8 failed steps!
brew test --retry --verbose byteman
brew test --retry --verbose fits
brew test --retry --verbose jasmin
brew test --retry --verbose jetty
brew install --build-from-source man-db
brew install --build-from-source mesos
brew install --build-from-source planck
brew install --build-from-source simutrans

Mojave

Error: 5 failed steps!
brew test --retry --verbose byteman
brew test --retry --verbose fits
brew test --retry --verbose jasmin
brew test --retry --verbose jetty
brew install --build-from-source planck

@jonchang
Copy link
Contributor

Looks like adoptopenjdk is using 15.0.2+7 🤷

@BrewTestBot
Copy link
Member

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@BrewTestBot BrewTestBot added the stale No recent activity label Feb 28, 2021
BrewTestBot pushed a commit that referenced this pull request Mar 1, 2021
Needed for #69460

Closes #72153.

Signed-off-by: Carlo Cabrera <30379873+carlocab@users.noreply.github.com>
Signed-off-by: Jonathan Chang <me@jonathanchang.org>
@jonchang
Copy link
Contributor

jonchang commented Mar 2, 2021

mesos and man-db are now fixed, so hopefully this CI run works.

@BrewTestBot BrewTestBot removed the stale No recent activity label Mar 2, 2021
@jonchang
Copy link
Contributor

jonchang commented Mar 3, 2021

Mojave is 🍏 🙏

@carlocab
Copy link
Member

carlocab commented Mar 3, 2021

Big Sur:

Error: 4 failed steps!
rm -rf /Users/brew/Library/Caches/Homebrew
brew install --build-from-source emscripten
rm -rf /Users/brew/Library/Caches/Homebrew
brew install --build-from-source varnish

Catalina:

Error: 2 failed steps!
brew install --build-from-source root
brew install --build-from-source varnish

emscripten:

cp: /private/tmp/emscripten--llvm-20210302-46554-1i290gk/.git/packed-refs: No space left on device

varnish: #72404

root:

==> brew install --build-from-source root
==> FAILED
==> Downloading https://root.cern.ch/download/root_v6.22.06.source.tar.gz
curl: (56) LibreSSL SSL_read: error:06FFF064:digital envelope routines:CRYPTO_internal:bad decrypt, errno 0
Error: Failed to download resource "root"
Download failed: https://root.cern.ch/download/root_v6.22.06.source.tar.gz

A little surprised the ARM runner is still going.

@carlocab
Copy link
Member

carlocab commented Mar 4, 2021

ARM runner is still going. It seems to be weird to have to wait for it, given that this PR should have no impact on the ARM bottle other than renaming it...

@jonchang
Copy link
Contributor

jonchang commented Mar 5, 2021

I'm just going to publish these bottles. OpenJDK 16 is coming out in a few weeks so we need to direct our energy there 🤷

@BrewTestBot
Copy link
Member

:shipit: @jonchang has triggered a merge.

@jonchang
Copy link
Contributor

jonchang commented Mar 5, 2021

I logged into the ARM runner and determined that an automatic update (of the runner) seemed to have killed the runner instance, which is why the tests were stalled.

@el7cosmos el7cosmos deleted the bump-openjdk-15.0.2 branch March 5, 2021 02:55
@BrewTestBot BrewTestBot added the outdated PR was locked due to age label Apr 6, 2021
@Homebrew Homebrew locked as resolved and limited conversation to collaborators Apr 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated PR was locked due to age
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants