Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 844034 - dev-ruby/hiera-eyaml-3.2.2 fails tests on arm64
Summary: dev-ruby/hiera-eyaml-3.2.2 fails tests on arm64
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Sysadmin Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 734842
  Show dependency tree
 
Reported: 2022-05-13 14:03 UTC by Jakov Smolić
Modified: 2023-03-27 08:44 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build log (ruby,197.31 KB, text/plain)
2022-05-13 14:03 UTC, Jakov Smolić
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jakov Smolić archtester gentoo-dev 2022-05-13 14:03:14 UTC
[31m(<unknown>): found character that cannot start any token while scanning for the next token at line 2 column 1 (Psych::SyntaxError)[0m
[31m./features/step_definitions/decrypt_steps.rb:4:in `/the output should have a key of '(.*?)' with ([0-9]*?) lines/'[0m
[31mfeatures/valid_encryption.feature:16:in `the output should have a key of 'key' with 3 lines'[0m

[31m(<unknown>): found character that cannot start any token while scanning for the next token at line 2 column 1 (Psych::SyntaxError)[0m
[31m./features/step_definitions/decrypt_steps.rb:4:in `/the output should have a key of '(.*?)' with ([0-9]*?) lines/'[0m
[31mfeatures/valid_encryption.feature:21:in `the output should have a key of 'key' with 3 lines'[0m

[31mFailing Scenarios:[0m
[31mcucumber features/config.feature:3[0m[90m # Scenario: uses default from eyaml when no config file[0m
[31mcucumber features/config.feature:9[0m[90m # Scenario: uses default from configuration file[0m
[31mcucumber features/config.feature:16[0m[90m # Scenario: uses default from configuration file supplied by a environment variable[0m
[31mcucumber features/decrypts.feature:7[0m[90m # Scenario: decrypt a simple string[0m
[31mcucumber features/decrypts.feature:11[0m[90m # Scenario: decrypt a default encryption string[0m
[31mcucumber features/decrypts.feature:15[0m[90m # Scenario: decrypt an encrypted file[0m
[31mcucumber features/decrypts.feature:19[0m[90m # Scenario: decrypt an eyaml file[0m
[31mcucumber features/decrypts.feature:40[0m[90m # Scenario: decrypt using STDIN[0m
[31mcucumber features/edit.feature:7[0m[90m # Scenario: decrypt an eyaml file[0m
[31mcucumber features/edit.feature:33[0m[90m # Scenario: decrypting a eyaml file should create a temporary file[0m
[31mcucumber features/edit.feature:45[0m[90m # Scenario: decrypting a eyaml file with --no-preamble should NOT add a preamble[0m
[31mcucumber features/edit.feature:57[0m[90m # Scenario: editing a non-existant eyaml file should give you a blank file[0m
[31mcucumber features/edit.feature:63[0m[90m # Scenario: editing a non-existant eyaml file should save a new file[0m
[31mcucumber features/edit.feature:72[0m[90m # Scenario: decrypt and reencrypt an eyaml file[0m
[31mcucumber features/edit.feature:96[0m[90m # Scenario: decrypt and reencrypt an eyaml file with multiple new values[0m
[31mcucumber features/edit.feature:113[0m[90m # Scenario: not editing a file should result in a no changes detected message[0m
[31mcucumber features/edit.feature:125[0m[90m # Scenario: modifying the plaintext should result in an encryption[0m
[31mcucumber features/edit.feature:131[0m[90m # Scenario: editing but not modifying a eyaml file with --no-preamble should be detected[0m
[31mcucumber features/edit.feature:137[0m[90m # Scenario: no-decrypt mode should not decrypt input[0m
[31mcucumber features/edit.feature:144[0m[90m # Scenario: no-decrypt mode should encrypt new values[0m
[31mcucumber features/edit.feature:159[0m[90m # Scenario: no-decrypt mode should succeed even if keyfile is unreadable[0m
[31mcucumber features/edit.feature:168[0m[90m # Scenario: EDITOR has a space in it that isn't quoted or escaped[0m
[31mcucumber features/edit.feature:174[0m[90m # Scenario: EDITOR has a space in it that is escaped but not isn't quoted[0m
[31mcucumber features/edit.feature:180[0m[90m # Scenario: EDITOR has a space in it that is quoted[0m
[31mcucumber features/edit.feature:186[0m[90m # Scenario: EDITOR is an executable on PATH[0m
[31mcucumber features/edit.feature:193[0m[90m # Scenario: EDITOR is an executable on PATH and contains arguments[0m
[31mcucumber features/edit.feature:201[0m[90m # Scenario: EDITOR is an executable on PATH and has a space in it that isn't quoted or escaped[0m
[31mcucumber features/edit.feature:208[0m[90m # Scenario: EDITOR is an executable on PATH and has a space in it that is escaped but not quoted[0m
[31mcucumber features/edit.feature:215[0m[90m # Scenario: EDITOR is an executable on PATH and has a space in it that is quoted[0m
[31mcucumber features/edit.feature:222[0m[90m # Scenario: EDITOR is an executable on PATH and has a space in it and contains arguments[0m
[31mcucumber features/edit.feature:230[0m[90m # Scenario: EDITOR is invalid[0m
[31mcucumber features/encrypts.feature:7[0m[90m # Scenario: encrypt a simple string[0m
[31mcucumber features/encrypts.feature:11[0m[90m # Scenario: encrypt a simple file[0m
[31mcucumber features/encrypts.feature:15[0m[90m # Scenario: encrypt a eyaml file[0m
[31mcucumber features/encrypts.feature:19[0m[90m # Scenario: encrypt a binary file[0m
[31mcucumber features/encrypts.feature:23[0m[90m # Scenario: encrypt a password[0m
[31mcucumber features/encrypts.feature:27[0m[90m # Scenario: encrypt using STDIN[0m
[31mcucumber features/encrypts.feature:31[0m[90m # Scenario: encrypt as string with a label[0m
[31mcucumber features/encrypts.feature:35[0m[90m # Scenario: encrypt as block with a label[0m
[31mcucumber features/keys.feature:7[0m[90m # Scenario: create some pkcs7 keys[0m
[31mcucumber features/keys.feature:11[0m[90m # Scenario: create missing pkcs7 keys dir[0m
[31mcucumber features/keys.feature:15[0m[90m # Scenario: create some plaintext keys[0m
[31mcucumber features/outputs.feature:8[0m[90m # Scenario: encrypt a simple string with default output[0m
[31mcucumber features/outputs.feature:13[0m[90m # Scenario: encrypt a simple string with examples output[0m
[31mcucumber features/outputs.feature:18[0m[90m # Scenario: encrypt a simple string with string output[0m
[31mcucumber features/outputs.feature:22[0m[90m # Scenario: encrypt a simple string with raw output[0m
[31mcucumber features/outputs.feature:27[0m[90m # Scenario: encrypt a simple string with block output[0m
[31mcucumber features/plugin.feature:7[0m[90m # Scenario: encrypt using plaintext plugin[0m
[31mcucumber features/plugin.feature:11[0m[90m # Scenario: decrypt using plaintext plugin[0m
[31mcucumber features/plugin.feature:15[0m[90m # Scenario: decrypt using inferred plugin[0m
[31mcucumber features/plugin.feature:19[0m[90m # Scenario: decrypt using forced plaintext plugin[0m
[31mcucumber features/plugin.feature:23[0m[90m # Scenario: decrypt using two plugins[0m
[31mcucumber features/plugin.feature:27[0m[90m # Scenario: decrypt using two plugins with default plaintext[0m
[31mcucumber features/plugin.feature:31[0m[90m # Scenario: decrypt using two plugins with default pkcs7[0m
[31mcucumber features/plugin_api.feature:7[0m[90m # Scenario: verify plugin options are available in eyaml[0m
[31mcucumber features/plugin_api.feature:13[0m[90m # Scenario: exercise plugin options for a plugin[0m
[31mcucumber features/puppet.feature:7[0m[90m # Scenario: verify puppet with hiera can use hiera-eyaml to decrypt data[0m
[31mcucumber features/puppet.feature:18[0m[90m # Scenario: verify puppet with hiera can use hiera-eyaml to decrypt data with keys as environment variables[0m
[31mcucumber features/puppet.feature:30[0m[90m # Scenario: verify puppet and facter for correct hash merge with incorrect fact[0m
[31mcucumber features/puppet.feature:41[0m[90m # Scenario: verify puppet and facter for correct hash merge[0m
[31mcucumber features/recrypt.feature:30[0m[90m # Scenario: Recrypt encrypted yaml using the eyaml tool[0m
[31mcucumber features/valid_encryption.feature:3[0m[90m # Scenario: encrypt and decrypt a binary file[0m
[31mcucumber features/valid_encryption.feature:9[0m[90m # Scenario: encrypt and decrypt a simple file[0m
[31mcucumber features/valid_encryption.feature:14[0m[90m # Scenario: encrypt and decrypt multiline yaml[0m
[31mcucumber features/valid_encryption.feature:19[0m[90m # Scenario: encrypt and decrypt windows multiline yaml[0m

78 scenarios ([31m65 failed[0m, [32m13 passed[0m)
402 steps ([31m65 failed[0m, [36m111 skipped[0m, [32m226 passed[0m)
0m40.677s
[1m[32m┌──────────────────────────────────────────────────────────────────────────────┐[0m[0m
[1m[32m│[0m[0m Share your Cucumber Report with your team at [4m[1m[36mhttps://reports.cucumber.io[0m[0m[0m     [1m[32m│[0m[0m
[1m[32m│[0m[0m                                                                              [1m[32m│[0m[0m
[1m[32m│[0m[0m Command line option:    [36m--publish[0m                                            [1m[32m│[0m[0m
[1m[32m│[0m[0m Environment variable:   [36mCUCUMBER_PUBLISH_ENABLED[0m=[36mtrue[0m                        [1m[32m│[0m[0m
[1m[32m│[0m[0m cucumber.yml:           [36mdefault: --publish[0m                                   [1m[32m│[0m[0m
[1m[32m│[0m[0m                                                                              [1m[32m│[0m[0m
[1m[32m│[0m[0m More information at [4m[1m[36mhttps://cucumber.io/docs/cucumber/environment-variables/[0m[0m[0m [1m[32m│[0m[0m
[1m[32m│[0m[0m                                                                              [1m[32m│[0m[0m
[1m[32m│[0m[0m To disable this message, specify [1mCUCUMBER_PUBLISH_QUIET=true[0m or use the      [1m[32m│[0m[0m
[1m[32m│[0m[0m [1m--publish-quiet[0m option. You can also add this to your [1mcucumber.yml:[0m          [1m[32m│[0m[0m
[1m[32m│[0m[0m [1mdefault: --publish-quiet[0m                                                     [1m[32m│[0m[0m
[1m[32m└──────────────────────────────────────────────────────────────────────────────┘[0m[0m
 * ERROR: dev-ruby/hiera-eyaml-3.2.2::gentoo failed (test phase):
 *   (no error message)
 * 
 * Call stack:
 *     ebuild.sh, line  127:  Called src_test
 *   environment, line 2198:  Called ruby-ng_src_test
 *   environment, line 1823:  Called _ruby_each_implementation 'each_ruby_test'
 *   environment, line  501:  Called _ruby_invoke_environment 'ruby26' 'each_ruby_test'
 *   environment, line  630:  Called each_ruby_test
 *   environment, line  866:  Called die
 * The specific snippet of code:
 *       ${RUBY} -S cucumber --format progress features || die
 * 
 * If you need support, post the output of `emerge --info '=dev-ruby/hiera-eyaml-3.2.2::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-ruby/hiera-eyaml-3.2.2::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-ruby/hiera-eyaml-3.2.2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-ruby/hiera-eyaml-3.2.2/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-ruby/hiera-eyaml-3.2.2/work/ruby26/hiera-eyaml-3.2.2'
 * S: '/var/tmp/portage/dev-ruby/hiera-eyaml-3.2.2/work/ruby26/hiera-eyaml-3.2.2'
Comment 1 Jakov Smolić archtester gentoo-dev 2022-05-13 14:03:59 UTC
Created attachment 778490 [details]
build log
Comment 2 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-03-27 08:44:59 UTC
Long obsolete version involving ancient (now last-rited) puppet-5.