apache/openwhisk

NamespaceSpecificThrottleTests is not properly cleaning up temporary subjects

Open

#2881 opened on Oct 21, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Scala (6,777 stars) (1,177 forks)batch import
good first issueheisenbugtesting

Description

limits.NamespaceSpecificThrottleTests > initializationError FAILED
    org.scalatest.exceptions.TestFailedException: python wskadmin user create zeroSubject
    Namespace already exists

    exit code: 1 was not equal to 0

a previous CI has failed to remove this subject, preventing future runs from completing.

Contributor guide

Tech stack
scala
Domain
testingbackend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic Scalatest cleanup concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
The test NamespaceSpecificThrottleTests fails because a previous test run left behind a temporary subject 'zeroSubject', causing a namespace conflict. To fix, add cleanup in the test's teardown method to delete the subject after each test or after the suite, using the wskadmin tool or an equivalent API. Look at the test file to understand the subject creation and ensure it is removed in afterEach or afterAll. No linked PR or comments suggest ongoing work, so the issue is open for contribution.