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.

Sign up for GitHub

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

Jump to bottom

Tests failure: Couldn't parse YAML Cannot look up attributes in a Cro::Tools::CroFile type object #68

Open
zoffixznet opened this issue May 15, 2018 · 2 comments
Open

Tests failure: Couldn't parse YAML Cannot look up attributes in a Cro::Tools::CroFile type object #68

zoffixznet opened this issue May 15, 2018 · 2 comments

Comments

@zoffixznet
Copy link

zoffixznet commented May 15, 2018 •
edited
Loading 

$ perl6 -v
This is Rakudo version 2018.04-20-g7847768 built on MoarVM version 2018.04-34-g25f165a
implementing Perl 6.c.

$ lsb_release -a
LSB Version:	core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID:	Ubuntu
Description:	Ubuntu 12.04 LTS
Release:	12.04
Codename:	precise

$ uname -a
Linux ZZZ 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

$ zef install cro
===> Searching for: cro
===> Found: cro:ver<0.7.5> [via Zef::Repository::Ecosystems<cpan>]
===> Dependencies: IO::Socket::Async::SSL, JSON::Fast, META6, Shell::Command, File::Find, Terminal::ANSIColor, OO::Monitors, YAMLish, Cro::WebSocket, Docker::File
===> Searching for missing dependencies: Cro::WebSocket
===> Found dependencies: Cro::WebSocket:ver<0.7.5> [via Zef::Repository::Ecosystems<cpan>]
===> Dependencies: Cro::HTTP, Base64, Digest::SHA1::Native, Crypt::Random, JSON::Fast
===> Searching for missing dependencies: Cro::HTTP
===> Found dependencies: Cro::HTTP:ver<0.7.5> [via Zef::Repository::Ecosystems<cpan>]
===> Dependencies: IO::Socket::Async::SSL, OO::Monitors, IO::Path::ChildSecure, Base64, HTTP::HPACK, Cro::Core, Cro::TLS, JSON::Fast, Crypt::Random, JSON::JWT, DateTime::Parse
===> Searching for missing dependencies: Cro::Core, Cro::TLS
===> Found dependencies: Cro::TLS:ver<0.7.5>, Cro::Core:ver<0.7.5> [via Zef::Repository::Ecosystems<cpan>]
===> Dependencies: Cro::Core, IO::Socket::Async::SSL
===> Fetching: cro
Fetching with plugin: Zef::Service::Shell::curl+{<anon|1>}
===> Fetching [OK]: cro:ver<0.7.5> to /home/zoffix/.zef/tmp/1526389807.27715.4584/cro-0.7.5.tar.gz
===> Fetching: Cro::WebSocket
Fetching with plugin: Zef::Service::Shell::curl+{<anon|1>}
===> Fetching [OK]: Cro::WebSocket:ver<0.7.5> to /home/zoffix/.zef/tmp/1526389809.27715.7513/cro-websocket-0.7.5.tar.gz
===> Fetching: Cro::HTTP
Fetching with plugin: Zef::Service::Shell::curl+{<anon|1>}
===> Fetching [OK]: Cro::HTTP:ver<0.7.5> to /home/zoffix/.zef/tmp/1526389810.27715.616/cro-http-0.7.5.tar.gz
===> Fetching: Cro::TLS
Fetching with plugin: Zef::Service::Shell::curl+{<anon|1>}
===> Fetching [OK]: Cro::TLS:ver<0.7.5> to /home/zoffix/.zef/tmp/1526389811.27715.5625/cro-tls-0.7.5.tar.gz
===> Fetching: Cro::Core
Fetching with plugin: Zef::Service::Shell::curl+{<anon|1>}
===> Fetching [OK]: Cro::Core:ver<0.7.5> to /home/zoffix/.zef/tmp/1526389811.27715.2157/cro-core-0.7.5.tar.gz
===> Extracting: cro
Extracting with plugin: Zef::Service::Shell::tar+{<anon|1>}
===> Extraction [OK]: cro to /home/zoffix/.zef/store/cro-0.7.5.tar.gz
===> Extracting: Cro::WebSocket
Extracting with plugin: Zef::Service::Shell::tar+{<anon|1>}
===> Extraction [OK]: Cro::WebSocket to /home/zoffix/.zef/store/cro-websocket-0.7.5.tar.gz
===> Extracting: Cro::HTTP
Extracting with plugin: Zef::Service::Shell::tar+{<anon|1>}
===> Extraction [OK]: Cro::HTTP to /home/zoffix/.zef/store/cro-http-0.7.5.tar.gz
===> Extracting: Cro::TLS
Extracting with plugin: Zef::Service::Shell::tar+{<anon|1>}
===> Extraction [OK]: Cro::TLS to /home/zoffix/.zef/store/cro-tls-0.7.5.tar.gz
===> Extracting: Cro::Core
Extracting with plugin: Zef::Service::Shell::tar+{<anon|1>}
===> Extraction [OK]: Cro::Core to /home/zoffix/.zef/store/cro-core-0.7.5.tar.gz
===> Filtering: cro:ver<0.7.5>
===> Filtering [OK] for cro:ver<0.7.5>
===> Filtering: Cro::WebSocket:ver<0.7.5>
===> Filtering [OK] for Cro::WebSocket:ver<0.7.5>
===> Filtering: Cro::HTTP:ver<0.7.5>
===> Filtering [OK] for Cro::HTTP:ver<0.7.5>
===> Filtering: Cro::TLS:ver<0.7.5>
===> Filtering [OK] for Cro::TLS:ver<0.7.5>
===> Filtering: Cro::Core:ver<0.7.5>
===> Filtering [OK] for Cro::Core:ver<0.7.5>
===> # SKIP: No need to build Cro::Core:ver<0.7.5>
===> # SKIP: No need to build Cro::TLS:ver<0.7.5>
===> # SKIP: No need to build Cro::HTTP:ver<0.7.5>
===> # SKIP: No need to build Cro::WebSocket:ver<0.7.5>
===> # SKIP: No need to build cro:ver<0.7.5>
===> Testing: Cro::Core:ver<0.7.5>
Testing with plugin: Zef::Service::Shell::prove+{<anon|1>}
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=1140, 13 wallclock secs ( 0.14 usr  0.02 sys + 12.06 cusr  0.59 csys = 12.81 CPU)
Result: PASS
===> Testing [OK] for Cro::Core:ver<0.7.5>
===> Testing: Cro::TLS:ver<0.7.5>
Testing with plugin: Zef::Service::Shell::prove+{<anon|1>}
t/tls.t .. ok
All tests successful.
Files=1, Tests=49, 11 wallclock secs ( 0.03 usr  0.00 sys +  9.57 cusr  0.46 csys = 10.06 CPU)
Result: PASS
===> Testing [OK] for Cro::TLS:ver<0.7.5>
===> Testing: Cro::HTTP:ver<0.7.5>
Testing with plugin: Zef::Service::Shell::prove+{<anon|1>}
t/http-auth-basic.t ............ ok
t/http-auth-webtoken-bearer.t .. ok
t/http-auth-webtoken-cookie.t .. ok
t/http-client.t ................ ok
t/http-cookie.t ................ ok
t/http-cookiejar.t ............. ok
t/http-log-file.t .............. ok
t/http-middleware.t ............ ok
t/http-request-parser.t ........ ok
t/http-request-serializer.t .... ok
t/http-request.t ............... ok
t/http-response-parser.t ....... ok
t/http-response-serializer.t ... ok
t/http-response.t .............. ok
t/http-router.t ................ ok
t/http-server.t ................ ok
t/http-session-inmemory.t ...... ok
t/http-session-persistent.t .... ok
t/http2-frame-parser.t ......... ok
t/http2-frame-serializer.t ..... ok
t/http2-frame.t ................ ok
t/http2-push-promise.t ......... ok
t/http2-request-parser.t ....... ok
t/http2-request-serializer.t ... ok
t/http2-response-parser.t ...... ok
t/http2-response-serializer.t .. ok
t/http2.t ...................... ok
t/router-auth.t ................ ok
t/uri-http.t ................... ok
All tests successful.
Files=29, Tests=1494, 179 wallclock secs ( 0.28 usr  0.03 sys + 157.66 cusr 10.20 csys = 168.17 CPU)
Result: PASS
===> Testing [OK] for Cro::HTTP:ver<0.7.5>
===> Testing: Cro::WebSocket:ver<0.7.5>
Testing with plugin: Zef::Service::Shell::prove+{<anon|1>}
t/http-router-websocket.t ......... ok
Cannot write to a closed socket
t/websocket-client.t .............. ok
t/websocket-frame-parser.t ........ ok
t/websocket-frame-serializer.t .... ok
t/websocket-handler.t ............. ok
t/websocket-message-parser.t ...... ok
t/websocket-message-serializer.t .. ok
t/websocket-message.t ............. ok
All tests successful.
Files=8, Tests=150, 42 wallclock secs ( 0.05 usr  0.02 sys + 36.62 cusr  2.71 csys = 39.40 CPU)
Result: PASS
===> Testing [OK] for Cro::WebSocket:ver<0.7.5>
===> Testing: cro:ver<0.7.5>
Testing with plugin: Zef::Service::Shell::prove+{<anon|1>}
t/tools-crofile.t ...... ok
t/tools-link-editor.t .. ok
# Check service up attempt 1: Timed out after 10s
# Check service up attempt 2: connection refused
# Check service up attempt 3: Timed out after 10s
# Check service up attempt 1: connection refused
# Check service up attempt 2: connection refused
# Check service up attempt 3: Timed out after 10s
t/tools-runner.t ....... ok
# Couldn't parse YAML
Cannot look up attributes in a Cro::Tools::CroFile type object
  in method id at /home/zoffix/.zef/store/cro-0.7.5.tar.gz/cro-0.7.5/lib/Cro/Tools/CroFile.pm6 (Cro::Tools::CroFile) line 28
  in block <unit> at t/tools-services.t line 58

t/tools-services.t ..... 
Dubious, test returned 1 (wstat 256, 0x100)
All 9 subtests passed 

Test Summary Report
-------------------
t/tools-services.t   (Wstat: 256 Tests: 9 Failed: 0)
  Non-zero exit status: 1
  Parse errors: No plan found in TAP output
Files=4, Tests=111, 60 wallclock secs ( 0.04 usr  0.01 sys + 36.97 cusr  2.48 csys = 39.50 CPU)
Result: FAIL
===> Testing [FAIL]: cro:ver<0.7.5>
Aborting due to test failure: cro:ver<0.7.5> (use --force-test to override)
  in code  at /home/zoffix/rakudo/install/share/perl6/site/sources/7926F4F3ED4C81AA5DA2A54C8AE1E03D03424CCE (Zef::Client) line 375
  in method test at /home/zoffix/rakudo/install/share/perl6/site/sources/7926F4F3ED4C81AA5DA2A54C8AE1E03D03424CCE (Zef::Client) line 355
  in code  at /home/zoffix/rakudo/install/share/perl6/site/sources/7926F4F3ED4C81AA5DA2A54C8AE1E03D03424CCE (Zef::Client) line 531
  in sub  at /home/zoffix/rakudo/install/share/perl6/site/sources/7926F4F3ED4C81AA5DA2A54C8AE1E03D03424CCE (Zef::Client) line 528
  in method install at /home/zoffix/rakudo/install/share/perl6/site/sources/7926F4F3ED4C81AA5DA2A54C8AE1E03D03424CCE (Zef::Client) line 623
  in sub MAIN at /home/zoffix/rakudo/install/share/perl6/site/sources/E4784A2A0FA00D16808817186E95FE74BEF3FE2D (Zef::CLI) line 152
  in block <unit> at /home/zoffix/rakudo/install/share/perl6/site/resources/3065D08F5332CA244672D7F8A05B603F92BB8A7D line 3
  in sub MAIN at /home/zoffix/rakudo/install/share/perl6/site/bin/zef line 2
  in block <unit> at /home/zoffix/rakudo/install/share/perl6/site/bin/zef line 2
@jnthn
Copy link
Member

jnthn commented Oct 16, 2018

This should, at the very least, give a more useful output now.

@jnthn
Copy link
Member

jnthn commented Oct 16, 2018

Ah, maybe not, actually; I misread which test it is.

jnthn added a commit that referenced this issue Oct 16, 2018
@jnthn
Try to better handle new service creation
3d982e2 
It might be that the `.cro.yml` file's creation triggers an file system
event, but the contents of the file wasn't written yet. If we see it's
an empty file, be a bit more patient. This is my best guess at the cause
of the failure reported in #68.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jnthn @zoffixznet