Skip to content

Commit

Permalink
Get rid of race condition in scale command int test
Browse files Browse the repository at this point in the history
This test just runs cf scale appName and prints the current state of the
app without actually updating it, it still might display 0/0 memory
depending on the state of CAPI after the push.  Since this comes from
log cache there could be a delay

Co-authored-by: Jenna Goldstrich <jgoldstrich@pivotal.io>
Co-authored-by: Seth Boyles <sboyles@pivotal.io>
  • Loading branch information
Jenna Goldstrich and sethboyles committed Mar 26, 2021
1 parent dbd8ec1 commit 2c953a1
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions integration/v7/isolated/scale_command_test.go
Original file line number Diff line number Diff line change
Expand Up @@ -125,8 +125,8 @@ var _ = Describe("scale command", func() {
Expect(processSummary.InstanceCount).To(Equal("1/1"))

instanceSummary := processSummary.Instances[0]
Expect(instanceSummary.Memory).To(MatchRegexp(`\d+(\.\d+)?[KMG]? of \d+[KMG]`))
Expect(instanceSummary.Disk).To(MatchRegexp(`\d+(\.\d+)?[KMG]? of \d+[KMG]`))
Expect(instanceSummary.Memory).To(MatchRegexp(`\d+(\.\d+)?[KMG]? of \d+?[KMG]?`))
Expect(instanceSummary.Disk).To(MatchRegexp(`\d+(\.\d+)?[KMG]? of \d+?[KMG]?`))

Expect(appTable.Processes[1].Type).To(Equal("console"))
Expect(appTable.Processes[1].InstanceCount).To(Equal("0/0"))
Expand Down

0 comments on commit 2c953a1

Please sign in to comment.