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

[WIP] Blin 2019-08-20 #3132

Closed
9 of 11 tasks
AlexDaniel opened this issue Aug 22, 2019 · 19 comments
Closed
9 of 11 tasks

[WIP] Blin 2019-08-20 #3132

AlexDaniel opened this issue Aug 22, 2019 · 19 comments
Labels
blin Result of a regular ecosystem check with modules regressed, which must be fixed before release BLOCKER Preventing the next release of rakudo, or just needing attention before the release

Comments

@AlexDaniel
Copy link
Contributor

AlexDaniel commented Aug 22, 2019

All these should be fixed with 0dd6573:

  • DBIish – Fail, Bisected: c7056f2
  • GraphQL – Fail, Bisected: c7056f2
  • MinG – Fail, Bisected: c7056f2
  • URI::Template – Fail, Bisected: c7056f2
  • XML::Class – Fail, Bisected: c7056f2
  • YAMLish – Fail, Bisected: c7056f2
  • Yapsi – Fail, Bisected: c7056f2

Raw Blin files: https://usercontent.irccloud-cdn.com/file/Kuaq7HLm/blin-output-2019-08-20.tar.gz

Previous ticket: #3113

From the previous ticket (we need to figure out what was wrong there anyway):

  • Smack – Fail, Bisected: fcf1f76
@AlexDaniel AlexDaniel added the BLOCKER Preventing the next release of rakudo, or just needing attention before the release label Aug 22, 2019
@AlexDaniel AlexDaniel mentioned this issue Aug 22, 2019
8 tasks
@AlexDaniel
Copy link
Contributor Author

There's a golf for c7056f2 issues here: c7056f2#commitcomment-34749749

@salortiz
Copy link
Contributor

@AlexDaniel,
The issue with c7056f2 was fixed with 0dd6573
Regards.

@AlexDaniel
Copy link
Contributor Author

Yes, got that! Thank you!

@AlexDaniel
Copy link
Contributor Author

AlexDaniel commented Aug 29, 2019

From the last Blin run:

  • API::USNavalObservatory – Fail, Bisected: 43066b9
  • App::AizuOnlineJudge – Fail, Bisected: 43066b9
  • App::Assixt – Fail, Bisected: 43066b9
  • App::Tasks – Fail, Bisected: 43066b9
  • Audio::Icecast – Fail, Bisected: 43066b9
  • Config::Parser::yaml – Fail, Bisected: 43066b9
  • Cro::Core – Fail, Bisected: 43066b9
  • Cro::HTTP::Test – Fail, Bisected: 43066b9
  • Cro::OpenAPI::RoutesFromDefinition – Fail, Bisected: 43066b9
  • Cro::RPC::JSON – Fail, Bisected: 43066b9
  • Cro::WebApp – Fail, Bisected: 43066b9
  • CroX::HTTP::FallbackPassthru – Fail, Bisected: 43066b9
  • FanFou – Fail, Bisected: 43066b9
  • Hastebin – Fail, Bisected: 43066b9
  • I18n::Simple – Fail, Bisected: 43066b9
  • LogP6 – Fail, Bisected: 43066b9
  • LogP6-Writer-Journald – Fail, Bisected: 43066b9
  • Magento – Fail, Bisected: 43066b9
  • Monitor::Monit – Fail, Bisected: 43066b9
  • Net::Telnet – Fail, Bisected: 43066b9
  • Oddmuse6 – Fail, Bisected: 43066b9
  • OpenAPI::Model – Fail, Bisected: 43066b9
  • Sparrow6 – Fail, Bisected: 43066b9
  • Template::Classic – Fail, Bisected: 43066b9
  • Test::HTTP::Server – Fail, Bisected: 43066b9
  • Tomtit – Fail, Bisected: 43066b9
  • Tomty – Fail, Bisected: 43066b9
  • WebService::Soundcloud – Fail, Bisected: 43066b9

Ping @vrurg.

Blin output: https://usercontent.irccloud-cdn.com/file/FuRvVGH3/blin-output-2019-08-29.tar.gz

<japhb> AlexDaniel: Not looking at the tarball, but if you're seeing a lot of failed installs, it might be because YAMLish won't install right now. Author is aware.
<japhb> Leont/yamlish#29

There are many modules depending on YAMLish, but YAMLish was bisected to a different commit (c7056f2), but issues in that commit were already fixed, so it's just a bisection detail.

@AlexDaniel
Copy link
Contributor Author

AlexDaniel commented Aug 29, 2019

Something related to grammar .parse:

  • RDF::Turtle – Fail, Bisected: b21a577
  • DNS::Zone – Fail, Bisected: b21a577
  • TAP – Fail, Bisected: b21a577

@jnthn
Copy link
Member

jnthn commented Aug 29, 2019

About 43066b9, I mentioned when the 6.e grammar base class was being discussed that there should also be another meta-class (a 6.e GrammarHOW), which the 6.e BOOTSTRAP can then configure with the 6.e Grammar. That meta-class can go either in BOOTSTRAP or even in the 6.e setting. That would avoid this issue. Trying to do it with the approach taken here is not going to end well.

@AlexDaniel
Copy link
Contributor Author

AlexDaniel commented Aug 29, 2019

Other bisected modules, but these may be a bit spurious:

  • CoreHackers::Sourcery – Fail, Bisected: c94f5db
  • Cro::WebSocket – Fail, Bisected: 38aa128
  • Grammar::PrettyErrors – Fail, Bisected: da65fb5
  • Proc::Q – Fail, Bisected: f53c828

@vrurg
Copy link
Member

vrurg commented Aug 29, 2019

I think most of the problems related to 43066b9 are caused by broken TAP module. I already know what's the problem is.

@jnthn I would still be in favor of avoiding version-specific metaclasses.

@jnthn
Copy link
Member

jnthn commented Aug 29, 2019

I think most of the problems related to 43066b9 are caused by broken TAP module. I already know what's the problem is.

I think they're all because we find the wrong Grammar, because it's perfectly fine (and even fairly common) for modules to use that name within a module, and so have it registered lexically.

I would still be in favor of avoiding version-specific metaclasses.

Why? If we did that, we'd not have the problem exhibited here. And, more deeply, it feels entirely right to me: the default parent is a meta-behavior, and if we're already having another version of a behavior, I don't see why we shouldn't have another version of the related meta-behavior too.

@vrurg
Copy link
Member

vrurg commented Aug 29, 2019

I think they're all because we find the wrong Grammar, because it's perfectly fine (and even fairly common) for modules to use that name within a module, and so have it registered lexically.

Aha. I had to limit symbol lookup to setting, but used lexical lookup on client.

Why? If we did that, we'd not have the problem exhibited here. And, more deeply, it feels entirely right to me: the default parent is a meta-behavior, and if we're already having another version of a behavior, I don't see why we shouldn't have another version of the related meta-behavior too.

Perl6::Metaclass::Grammar6eHOW? Definitely not.

Language-specific meta? Should be possible, but not yet supported by the build subsystem. I have started process of merging common parts of moar and jvm makefiles and it turns out to be even more time consuming than I expected.

But otherwise the first thing coming to my mind is Perl6::Metamodel::v6<rev> and use Perl6::Metamodel::v6<rev>; in revision's BOOTSTRAP.

@vrurg
Copy link
Member

vrurg commented Aug 30, 2019

  • API::USNavalObservatory – Fail, Bisected: 43066b9
  • App::AizuOnlineJudge – Fail, Bisected: 43066b9
  • App::Assixt – Fail, Bisected: 43066b9
  • App::Tasks – Fail, Bisected: 43066b9 - can't clone for testing, but zef installs it
  • Audio::Icecast – Fail, Bisected: 43066b9
  • Config::Parser::yaml – Fail, Bisected: 43066b9
  • Cro::Core – Fail, Bisected: 43066b9
  • Cro::HTTP::Test – Fail, Bisected: 43066b9
  • Cro::OpenAPI::RoutesFromDefinition – Fail, Bisected: 43066b9
  • Cro::RPC::JSON – Fail, Bisected: 43066b9
  • Cro::WebApp – Fail, Bisected: 43066b9
  • CroX::HTTP::FallbackPassthru – Fail, Bisected: 43066b9
  • FanFou – Fail, Bisected: 43066b9
  • Hastebin – Fail, Bisected: 43066b9
  • I18n::Simple – Fail, Bisected: 43066b9
  • LogP6 – Fail, Bisected: 43066b9
  • LogP6-Writer-Journald – Fail, Bisected: 43066b9
  • Magento – Fail, Bisected: 43066b9
  • Monitor::Monit – Fail, Bisected: 43066b9
  • Net::Telnet – Fail, Bisected: 43066b9
  • Oddmuse6 – Fail, Bisected: 43066b9
  • OpenAPI::Model – Fail, Bisected: 43066b9
  • Sparrow6 – Fail, Bisected: 43066b9
  • Template::Classic – Fail, Bisected: 43066b9
  • Test::HTTP::Server – Fail, Bisected: 43066b9
  • Tomtit – Fail, Bisected: 43066b9
  • Tomty – Fail, Bisected: 43066b9
  • WebService::Soundcloud – Fail, Bisected: 43066b9

@vrurg
Copy link
Member

vrurg commented Aug 30, 2019

#3154 fixes all reported modules except for Grammar::PrettyErrors. I will merge the PR and then proceed with the latter. Though due to approaching hurricane not sure how much time would I have these days.

@AlexDaniel
Copy link
Contributor Author

Thank you, @vrurg! Please take care.

@vrurg
Copy link
Member

vrurg commented Aug 31, 2019

Re-implementing #3154 to conform with @jnthn request. Thus, all module checks would be re-done.

vrurg added a commit to vrurg/roast that referenced this issue Sep 1, 2019
It must be possible to create grammars named `Grammar`

rakudo/rakudo#3132
vrurg added a commit to vrurg/roast that referenced this issue Sep 1, 2019
It must be possible to create grammars named `Grammar`

rakudo/rakudo#3132
@vrurg
Copy link
Member

vrurg commented Sep 1, 2019

Grammar::PrettyErrors got a PR bduggan/raku-grammar-prettyerrors#1

@vrurg
Copy link
Member

vrurg commented Sep 2, 2019

All failures fixed with c757ada and with the above mentioned PR.

vrurg added a commit to Raku/roast that referenced this issue Sep 2, 2019
Test for 6.e grammar `Grammar` name

It must be possible to create grammars named `Grammar`

rakudo/rakudo#3132
@AlexDaniel
Copy link
Contributor Author

Here are the latest results. Seems previous issues are not resolved? @vrurg, can you check?

Raw data: https://usercontent.irccloud-cdn.com/file/WWEU5lHe/blin-output-2019-09-06.tar.gz

  • API::USNavalObservatory – Fail, Bisected: 43066b9
  • App::AizuOnlineJudge – Fail, Bisected: 43066b9
  • App::Assixt – Fail, Bisected: 43066b9
  • App::Tasks – Fail, Bisected: 43066b9
  • Audio::Icecast – Fail, Bisected: 43066b9
  • Config::Parser::yaml – Fail, Bisected: 43066b9
  • Cro::Core – Fail, Bisected: 43066b9
  • Cro::HTTP::Test – Fail, Bisected: 43066b9
  • Cro::OpenAPI::RoutesFromDefinition – Fail, Bisected: 43066b9
  • Cro::RPC::JSON – Fail, Bisected: 43066b9
  • Cro::WebApp – Fail, Bisected: 43066b9
  • CroX::HTTP::FallbackPassthru – Fail, Bisected: 43066b9
  • FanFou – Fail, Bisected: 43066b9
  • Hastebin – Fail, Bisected: 43066b9
  • I18n::Simple – Fail, Bisected: 43066b9
  • LogP6 – Fail, Bisected: 43066b9
  • LogP6-Writer-Journald – Fail, Bisected: 43066b9
  • Magento – Fail, Bisected: 43066b9
  • Monitor::Monit – Fail, Bisected: 43066b9
  • Net::Telnet – Fail, Bisected: 43066b9
  • Oddmuse6 – Fail, Bisected: 43066b9
  • OpenAPI::Model – Fail, Bisected: 43066b9
  • Sparrow6 – Fail, Bisected: 43066b9
  • Template::Classic – Fail, Bisected: 43066b9
  • Test::HTTP::Server – Fail, Bisected: 43066b9
  • Tomtit – Fail, Bisected: 43066b9
  • Tomty – Fail, Bisected: 43066b9
  • WebService::Soundcloud – Fail, Bisected: 43066b9

  • ASN::META – Fail, Bisected: 2ee82af
  • Cro::WebSocket – Fail, Bisected: 38aa128

  • DNS::Zone – Fail, Bisected: b21a577
  • RDF::Turtle – Fail, Bisected: b21a577
  • TAP – Fail, Bisected: b21a577

  • URI::Template – Fail, Bisected: c7056f2
  • YAMLish – Fail, Bisected: c7056f2

  • CoreHackers::Sourcery – Fail, Bisected: c94f5db
  • Grammar::PrettyErrors – Fail, Bisected: da65fb5
  • Proc::Q – Fail, Bisected: f53c828
  • Unicode::GCB – Fail, Bisected: f5ef0b3

@vrurg
Copy link
Member

vrurg commented Sep 6, 2019

@AlexDaniel check if it was ran against HEAD and there was no mistake. Cro::Core on freshly build HEAD from official repo, not the fork of mine:

🅸 ttys000 vrurg@beetle ~/s/P/c/cro-core ⇒ prove6 -l                                                                                                                                                                                                                                                                                                           -1- 06-09-19 10:49:49 [master]
t/composer.t ................ ok
t/connection-conditional.t .. ok
t/connection-state.t ........ ok
t/iri.t ..................... ok
t/mediatype.t ............... ok
t/message-with-body.t ....... ok
t/tcp.t ..................... ok
t/uri.t ..................... ok
All tests successful.
Files=8, Tests=1164,  11 wallclock secs
Result: PASS

There must be something else.

@AlexDaniel
Copy link
Contributor Author

@vrurg thank you for your work!

It's time for a new ticket.

@AlexDaniel AlexDaniel added the blin Result of a regular ecosystem check with modules regressed, which must be fixed before release label Jun 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blin Result of a regular ecosystem check with modules regressed, which must be fixed before release BLOCKER Preventing the next release of rakudo, or just needing attention before the release
Projects
None yet
Development

No branches or pull requests

4 participants