Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

badge and pipeline changes for main=>3.x and latest=> main #373

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

only show badges for main, remove branch filter

ab82b51
Select commit
Loading
Failed to load commit list.
Draft

badge and pipeline changes for main=>3.x and latest=> main #373

only show badges for main, remove branch filter
ab82b51
Select commit
Loading
Failed to load commit list.
Azure Pipelines / Steeltoe-Samples-Connectors-RabbitMQ failed Feb 11, 2025 in 9m 17s

Build #20250211.7 had test failures

1 errors / 0 warnings

Details

Tests

  • Failed: 1 (50.00%)
  • Passed: 0 (0.00%)
  • Other: 1 (50.00%)
  • Total: 2

Annotations

Check failure on line 192 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Steeltoe-Samples-Connectors-RabbitMQ

Build log #L192 

Bash exited with code '1'.

Check failure on line 1 in Rabbit Connector (net8.0/windows)

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Steeltoe-Samples-Connectors-RabbitMQ

Rabbit Connector (net8.0/windows) 

command returned non-zero return code: 1, stderr:
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Start unsuccessful

TIP: use 'cf logs rabbitmq-connector-sample --recent' for more information
Raw output 
Failing step: And you run: cf push -f manifest-windows.yml -p bin/Release/net8.0/win-x64/publish ... failed in 446.272s
Location: Connectors/src/RabbitMQ/RabbitMQ.feature:10
Traceback (most recent call last):
  File "/home/vsts/.local/share/virtualenvs/s-8OsOGiLq/lib/python3.11/site-packages/behave/model.py", line 1329, in run
    match.run(runner.context)
  File "/home/vsts/.local/share/virtualenvs/s-8OsOGiLq/lib/python3.11/site-packages/behave/matchers.py", line 98, in run
    self.func(context, *args, **kwargs)
  File "steps/process_steps.py", line 38, in step_impl
    Command(context, command).run()
  File "/home/vsts/work/1/s/pysteel/command.py", line 92, in run
    raise CommandException(
pysteel.command.CommandException: command returned non-zero return code: 1, stderr:
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Instances starting...
Start unsuccessful

TIP: use 'cf logs rabbitmq-connector-sample --recent' for more information
View more details on Azure Pipelines