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

Update samples #340

Merged
merged 8 commits into from
Sep 4, 2024

Correct spelling of Cloud Foundry

596c7f0
Select commit
Loading
Failed to load commit list.
Merged

Update samples #340

Correct spelling of Cloud Foundry
596c7f0
Select commit
Loading
Failed to load commit list.
Azure Pipelines / Steeltoe-Samples-Connectors-RabbitMQ succeeded Sep 4, 2024 in 9m 50s

Build #20240904.3 had test failures

0 errors / 0 warnings

Details

Tests

  • Failed: 1 (25.00%)
  • Passed: 2 (50.00%)
  • Other: 1 (25.00%)
  • Total: 4

Annotations

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...
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 app timeout

TIP: Application must be listening on the right port. Instead of hard coding the port, use the $PORT environment variable.

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 413.819s
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...
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 app timeout

TIP: Application must be listening on the right port. Instead of hard coding the port, use the $PORT environment variable.

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