apache/openwhisk

NamespaceSpecificThrottleTests is not properly cleaning up temporary subjects

Open

#2,881 建立於 2017年10月21日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Scala (6,777 star) (1,177 fork)batch import
good first issueheisenbugtesting

描述

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.

貢獻者指南

技術棧
scala
領域
testingbackend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
basic Scalatest cleanup concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
80
研究方向
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.