rspec: Metadata server on Google App Engine displays IP address read from metadata server failed about ruby-docs-samples

[SandeepTuniki]

There seems to be a mix-up of tests and the service being tested.

Below is the log for the failing test:

Failures:

  1) Metadata server on Google App Engine displays IP address read from metadata server
     Failure/Error:
       expect(response.body).to match(
         /External IP: \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}/
       )

       expected "Zone: projects/1092069843076/zones/us-east4-1" to match /External IP: \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}/
       Diff:
       @@ -1 +1 @@
       -/External IP: \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}/
       +"Zone: projects/1092069843076/zones/us-east4-1"
     # ./spec/metadata_server_spec.rb:29:in `block (2 levels) in <top (required)>'

Finished in 15.07 seconds (files took 0.2536 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spec/metadata_server_spec.rb:26 # Metadata server on Google App Engine displays IP address read from metadata server

**** FAILURE: SPEC:appengine/metadata_server

The expectation indicates that the spec being tested is appengine/metadata_server.

But the diff indicates that the test is executed against the service appengine/standard-metadata-server (based on the response containing Zone: ...).

We need to investigate why the wrong service is deployed for the test.

[flaky-bot]

commit: 71e8558
buildURL: Build Status, Sponge
status: failed

Test output

Failure/Error:
  expect(response.body).to match(
    /External IP: \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}/
  )
expected "\n\n<meta http-equiv="content-type" content="text/html;charset=utf-8">\n<title>404 P...t found\n
The requested URL was not found on this server.
\n
\n\n" to match /External IP: \d{1,3}.\d{1,3}.\d{1,3}.\d{1,3}/

Diff:

@@ -1,10 +1,19 @@

-/External IP: \d{1,3}.\d{1,3}.\d{1,3}.\d{1,3}/

+

+

+

+<title>404 Page not found</title>

+

+

+
Error: Page not found


+
The requested URL was not found on this server.


+


+

./spec/metadata_server_spec.rb:29:in `block (2 levels) in <top (required)>'

[flaky-bot]

Test passed for commit 50e0fbb (Build Status, Sponge)! Closing this issue.

[flaky-bot]

Looks like this issue is flaky. 😟

I'm going to leave this open and stop commenting.

A human should fix and close this.

---

commit: 5b53c09
buildURL: Build Status, Sponge
status: failed

Test output

Failure/Error:
  expect(response.body).to match(
    /External IP: \d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}/
  )
expected "\n\n<meta http-equiv="content-type" content="text/html;charset=utf-8">\n<title>502 S...ould not complete your request.
Please try again in 30 seconds.\n
\n\n" to match /External IP: \d{1,3}.\d{1,3}.\d{1,3}.\d{1,3}/

Diff:

@@ -1,10 +1,19 @@

-/External IP: \d{1,3}.\d{1,3}.\d{1,3}.\d{1,3}/

+

+

+

+<title>502 Server Error</title>

+

+

+
Error: Server Error


+
The server encountered a temporary error and could not complete your request.
Please try again in 30 seconds.


+


+

./spec/metadata_server_spec.rb:29:in `block (2 levels) in <top (required)>'

[NivedhaSenthil]

Test failures were happening because there are lot of versions deployed

ERROR: (gcloud.app.deploy) INVALID_ARGUMENT: Your app may not have more than 210 versions. Please delete one of the existing versions before trying to create a new version.

Upon checking the project it looks like the versions are cleaned up now, probably in the later runs. Hence closing this issue for now and keep an eye on it to see if it happens again.

[flaky-bot]

Oops! Looks like this issue is still flaky. It failed again. 😬

I reopened the issue, but a human will need to close it again.

---

commit: 9f3b81b
buildURL: Build Status, Sponge
status: failed