-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LIVEONLY tests in Storage #4147
Comments
Do you want storage team to look into this or you want to assign this to yourself just for tracking? |
@Jinming-Hu the help of your team would be greatly appreciated. |
Hi @gearama , I found some secrets were not properly redacted when fetching tokens. Can you update the sanitizer rule? |
Hi @gearama , have you got a chance to look at the above issue? What is the correct way to record/playback token-fetching/refreshing requests anyway? Is it by-design to not record such requests? |
There are some issues with test proxy behavior and some of the storage tests in a few cases there are errors around json deserialization "expected string received null", which suggest that the deserailization of the incoming json might not handle nulls properly.
The followin g tests i swiched to LIVEONLY
TEST_F(BlobBatchClientTest, DISABLED_SubmitDeleteBatch)
TEST_F(BlobBatchClientTest, DISABLED_SnapshotVersion
TEST_F(BlobBatchClientTest, DISABLED_TokenAuthorization)
TEST_F(QueueClientTest, PeekMessage_LIVEONLY_)
testlogs.zip
AppendBlobClientTest.ContentHash.zip
The text was updated successfully, but these errors were encountered: